Mergado handles secured feeds

Mergado can process a feed accessible under a login and a password. It can also retrieve that, even if the downloading is restricted to certain IP addresses. Let’s see how.

Feed accessible under a login and a password

Need to work with a password-protected feed? Enter this information in the feed URL.

Example:

https://login:password@www.your-online-store.com/feed.xml (where part after the @ sign is the url of your feed)

Feed protected for download from specific IP addresses only

Does your client require the feed to be protected only from specific IP addresses? It is sufficient to add the following IP addresses to the whitelist from which Mergado feeds are retrieved:

• 77.93.203.8
• 84.42.234.114
• 176.74.148.57
• 85.118.134.23
• 85.118.134.24
• 85.118.134.104
• 89.185.225.51
• 185.58.41.36
• 185.58.41.85
• 185.58.41.106
• 185.58.41.127
• 194.145.180.164
• 194.145.180.154
• 185.58.41.182

Note

The output URL for downloading from specific IP addresses cannot be secured.

However, there are a few protective factors:

1. The output URL contains a hash (a long string of characters). It is, therefore, not possible to guess the address. No one else, but the one to whom you give the address has no chance of revealing it.

2. The output feed download is logged and is available on the History page, where only events related to XML feed download can be filtered.

3. If the feed is downloaded by an unknown user-agent (other than a comparison engine), you will see it in the Download History, even after a few months.

You do not need to check individual pages of filtered Mergado Download History. You can download these selected events to CSV and then open them, for example, in Excel, where you can search for specific user-agents, easily group or filter the data.

Mergado is constantly working to improve its services. Do not doubt that it can appropriately protect data in your clients’ feeds.

You could be also interested in: