It is my understanding that iTunes does not update its feed URL when
it encounters a permanent redirect (HTTP status code 301). This makes
it impossible for publishers to permanently move their feeds to a new
location, since iTunes will continue to request the old location
forever unless the end user manually unsubscribes and resubscribes at
the new location. Yes, iTunes correctly follows the redirect, but
that only works as long as both locations are under the publisher's
control -- in effect, iTunes treats permanent and temporary redirects
the same.
This happens more frequently than you might think. People often start
publishing on one server, then (as they grow and need more
bandwidth/storage/control) they move to a new location -- perhaps
their own domain, perhaps a different domain with better hosting.
They need a way to tell iTunes to stop looking at the old location,
which may soon no longer be under their control once they stop paying
for it. HTTP permanent redirects are the standard way to do this.
Does Apple plan to fully support permanent HTTP redirects?
--
Cheers,
-Mark
_______________________________________________
Do not post admin requests to the list. They will be ignored.
syndication-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/syndication-dev/email@hidden
This email sent to email@hidden
