Hi, @jakearchibald, there is an open feature request for the docs change update about Large Media limitations with custom headers based on the other topic you linked to. We’ll post an update there (and here) when the docs are updated.
About the headers documentation it does say the following:
Paths can contain
*or:placeholders. A:placeholdermatches anything except/, while a*matches anything.
There are no examples which show that this can be used with a file extension. What wording would make it more clear that a file extension cannot be used? Would this be better?
Paths can contain
*or:placeholders. A:placeholdermatches anything except/, while a*matches anything.You cannot use
*to make rules like/*.htmlor/*/more/path/segments/. The*will match everything to the end of the line and.htmland/more/path/segments/would be ignored.
Regarding the deploy saying “All header rules deployed” despite the rules not working, would you please send us a link to that deploy?
Regarding removing Large Media would you please look over the following Support Guide?
That covers the steps involved. If you would then follow-up here with the identifier of the site, we’ll follow-up to let you know when the Large Media add-on is removed.