Changer un podcast de serveur
to2pac
-
Keni -
Keni -
Bonjour,
le fichier .xml regroupant les infos de mon podcast est hebergé sur un serveur.
Or je compte changer de serveur. Pourriez-vous m'indiquer la marche à suivre afin que le podcast fonctionne sur le nouveau serveur sans que j'ai à en créér un nouveau ?
J'ai regardé sur le site d'apple mais je n'ai rien trouvé de tres clair. Je crois qu'il y a une histoire de redirection mais je n'ai pas bien compris.
Merci d'avance pour votre aide
le fichier .xml regroupant les infos de mon podcast est hebergé sur un serveur.
Or je compte changer de serveur. Pourriez-vous m'indiquer la marche à suivre afin que le podcast fonctionne sur le nouveau serveur sans que j'ai à en créér un nouveau ?
J'ai regardé sur le site d'apple mais je n'ai rien trouvé de tres clair. Je crois qu'il y a une histoire de redirection mais je n'ai pas bien compris.
Merci d'avance pour votre aide
A voir également:
- Changer un podcast de serveur
- Changer dns - Guide
- Télécharger un podcast - Guide
- Podcast addict - Accueil - Guide audio
- Changer de carte graphique - Guide
- Changer extension fichier - Guide
1 réponse
You should use the <itunes:new-feed-url> tag described in the iTunes RSS Tags section below. The tag will cause the iTunes Store to be updated with the new feed URL, as well as all iTunes client versions that support podcasting.
You should set your web server to return an HTTP 301 response and redirect when receiving a request for the old feed. Doing so will cause both the iTunes Store and the most (but not all) iTunes clients that have subscribed to your podcast to pick up the new feed URL.
The <itunes:new-feed-url> tag will work for iTS and all versions of the iTunes client that support podcasting. The 301 redirect will work for most of your subscribers who do not use the iTunes client. We recommend that you use both methods to update the greatest possible number of subscribers with your new feed URL.
Be sure to maintain the <itunes:new-feed-url< tag and the 301 redirect for at least two weeks to ensure that most subscribers have attempted to download your most recent episode and have thereby received the new URL.
If you are not able to use both methods, you may want to include an audio note in your podcast, informing your subscribers that your podcast has changed locations.
You should set your web server to return an HTTP 301 response and redirect when receiving a request for the old feed. Doing so will cause both the iTunes Store and the most (but not all) iTunes clients that have subscribed to your podcast to pick up the new feed URL.
The <itunes:new-feed-url> tag will work for iTS and all versions of the iTunes client that support podcasting. The 301 redirect will work for most of your subscribers who do not use the iTunes client. We recommend that you use both methods to update the greatest possible number of subscribers with your new feed URL.
Be sure to maintain the <itunes:new-feed-url< tag and the 301 redirect for at least two weeks to ensure that most subscribers have attempted to download your most recent episode and have thereby received the new URL.
If you are not able to use both methods, you may want to include an audio note in your podcast, informing your subscribers that your podcast has changed locations.
