We've been asking for QueryStrings for content types that look like f?=.*
For some reason, this means that GET requests without ?f=anything are redirected to ones with ?f= appended. I don't know if this is bad, but it seems unclean.
If you change the QueryString to f=.* you get normal behavior
For example: https://geoconnex.us/ref/hu02/02 -> 303https://info.geoconnex.us/collections/hu02/items/02?f=
changing f?=. to f=. : https://geoconnex.us/ref/hu02/01 -> 303https://info.geoconnex.us/collections/hu02/items/01
I don't know if this breaks anything. I wonder if it has to do with the pygeoapi index issues we have been having (because what google infers the canonical URL to be based on all the alternate links doesn't exactly match what is redirected to).
Sad: have to change A LOT of PIDs
Happy: Can write something that recursively does all csvs and xml in the repo
Priority: lower than the main pygeoapi PRs that Greg is working on
We've been asking for QueryStrings for content types that look like
f?=.*
For some reason, this means that GET requests without
?f=anything
are redirected to ones with?f=
appended. I don't know if this is bad, but it seems unclean.If you change the QueryString to
f=.*
you get normal behaviorFor example:
https://geoconnex.us/ref/hu02/02
-> 303https://info.geoconnex.us/collections/hu02/items/02?f=
changing f?=. to f=. :
https://geoconnex.us/ref/hu02/01
-> 303https://info.geoconnex.us/collections/hu02/items/01
I don't know if this breaks anything. I wonder if it has to do with the pygeoapi index issues we have been having (because what google infers the canonical URL to be based on all the alternate links doesn't exactly match what is redirected to).
Sad: have to change A LOT of PIDs Happy: Can write something that recursively does all csvs and xml in the repo
Priority: lower than the main pygeoapi PRs that Greg is working on