@nathan Have you seen any negative consequences of sending the &_from= search param along with your enclosure urls?

Dave

@nathan Have you seen any negative consequences of sending the &_from= search param along with your enclosure urls? I know there was at least one hosting company that I can't remember which would return 403's if anything other than their strictly defined set of search params were present in the enclosure url. For some reason I'm thinking it's Podbean, but I can't remember.

Dave

@nathan Actually, maybe that was the feed urls that were being restricted so hard and not the enclosures now that I think more about it.

@js: have you seen anything like that?

John Spurlock

@dave @nathan the livewire feed validator has a workaround that prevents tacking on a cachebusting query param only for podbean

but always worth retesting this, as things change over time, also the validator works with feed urls, not enclosures

livewire-validator/validator-worker/common/validation_job_vm.ts at 31235309c3669963ec95468ecd74d2ab55060c2b · skymethod/livewire-validator

Podcast feed and media validator, including podcast namespace tags. - livewire-validator/validator-worker/common/validation_job_vm.ts at 31235309c3669963ec95468ecd74d2ab55060c2b · skymethod/livewire-validator

GitHub (github.com)