Outbound Feeds Requesting OBF Redirects
Outbound Feeds (OBF) replaced Arc XP’s legacy feeds service known as Arc I/O or partner-feeds (arcio). During your migration, the old and new systems continue to be available. This allows you to create your new feeds and then perform side-by-side comparisons on both systems to validate your feed and register the new URL with the appropriate system to get those services to find the new /arc/outboundfeeds
URLs.
What does an OBF redirect do?
Clients who are migrating from legacy feeds to OBF often need to redirect requests that were coming to /arcio/
to a corresponding /arc/outboundfeeds/
endpoint in order to effectively move clients. Feeds/urls
released to the internet cannot always be changed and require forced redirection. Arc XP does not support an open-ended request for redirection because there are many edge cases for redirect that could be asked for. Instead we provide a set of standard redirects that you can implement to redirect arcio
feeds on a feed-by-feed basis. Review the following restrictions to see the allowed request paths.
Examples
A client needs to redirect RSS feeds under /arcio/rss/
to a set of equivalent feeds under /arc/outboundfeeds/rss/
, a request for /arcio/rss/category/sports/
should redirect to /arc/outboundfeeds/rss/category/sports/?outputType=xml
, /arcio/rss/local/
should redirect to /arc/outboundfeeds/rss/local/?outpytType=xml
, etc.
Arc I/O | OBF |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* sitemap-section
is not a standard feed in arcio
Jira
ACS will implement the redirects as part of their normal support process. The turn around time for this request is five days.
Alternatively, for custom OBF redirects, you can use the Redirect tool in Delivery. See Configuring URL redirects.
Restrictions
The following redirect lines are supported. These paths correlate to the standard arcio
/OBF feeds that are provided by default. In addition to these, clients may ask for a single top level path in ArcIO to be redirected to the same top-level path in OBF, this is expected to be used to redirect custom feed’s created as part of classic feeds work. All redirects will be implemented as 301 permanent redirects. Rules may be implemented all at once or line by line as needed by the client.
Supported redirects |
---|
rewrite |
rewrite |
rewrite |
rewrite |
rewrite |
rewrite |
rewrite |
rewrite |
rewrite |
rewrite |
rewrite |
In the case where clients are requesting a custom top level path to be redirected use this template with customer provided path and outputType values:
Supported redirects |
---|
rewrite |
Legacy outbound feeds (partner-feeds)
To access your currently running feeds use the following links, replacing the bold values with your specific values.
Sandbox:
https://ORG-WEBSITE-sandbox.web.arc-cdn.net/arcio/FEED/
Production:
https://www.example.com/arcio/FEED/
Outbound feeds
To access your new Outbound Feeds use the following links, replacing the bold values with your specific values.
Sandbox:
https://ORG-WEBSITE-sandbox.web.arc-cdn.net/arc/outboundfeeds/FEED/?outputType=xml
Production:
https://www.example.com/arc/outboundfeeds/FEED/?outputType=xml