PB-1550 : Add a pre-processing hook to circumvent content-type mismatch #15
Conversation
|
@hansmannj @ltshb from my testing, this workaround doesn't seem to work as we get HTTP 406 errors when querying the search endpoint from STAC-Browser.
This is most likely due to the fact that our STAC implementation expects a "application/json" accept header. I've written a script to test this manually, and when switching to "application/geo+json", I get the same error when querying the search endpoint with a POST request :
Should we consider changing the search endpoint implementation?
|
| stac.conformsTo.push('https://api.stacspec.org/v1.0.0/item-search'); | ||
| stac.links = stac.links.map(link => { | ||
| if (link.rel === 'search') { | ||
| link.type = 'application/geo+json'; |
There was a problem hiding this comment.
I don't know the STAC browser code but I do know that we are currently unable to serve STAC content via application/geo+json, did you simply try to modify this line to application/json what our STAC supports ?
There was a problem hiding this comment.
Yes, but according to @m-mohr , the STAC-Browser has been made more restrictive on the matter, which is why our search feature no longer works - so I can't use application/json sadly
Based on @m-mohr 's suggestion