It's not possible to create XML feed in HTTPS

Products & SKU

Fixed
Julian Cecchi

Julian Cecchi

Last updated

Summary

Fixed
XML URLs now follow the same protocol configured for the product page.

The XML feeds link that is created uses HTTP instead of HTTPS.

When you configure the feed on external partner systems, such as Google, a redirection to an HTTPS link is generated and this causes the metric parameters to be lost.

You must use the HTTPS link to keep the metrics.

Simulation

  1. Access Catalog > Settings > XML
  2. Create an XML feed and get its URL
  3. This URL will be in HTTP and when using it on any system that requires HTTPS, a redirect must be made that will cause the parameters that come in the URL to be lost.

Workaround

Suggested architecture:

  1. We suggest using the Search API to consume the catalog;
  2. Generate the desired XML;
  3. Expose the XML in an environment with HTTPS that allows it to be consumed externally.

This strategy is not only a workaround but also the suggested strategy for scalability and XML feed handling in large catalogs since it’s possible to update the feed as often as needed, optimize the size of the XML and make it lighter, as well as have more product targeting options.