Leif Johansson
Leif Johansson
Note that this discussion is covered extensively in the seamlessaccess working groups on discovery hinting. The issue we are facing is exactly the same one that is faced by big...
Can you provide a sample URL that breaks?
Also feel free to provide a PR for quicker review but that URL would make a good testcase...
yeah this smells URL encoding fail to me somewhere - normally that == would/should have been URL-encoded before passing to pyFF because otherwize you could never do query-string parsing
Yeah you're right. I need to think about the right way to deal with this. Your patch at least solves one part of this so I don't mind applying it...
Is it still there in the wsgi api? Skickat från min iPhone > 26 aug. 2019 kl. 14:38 skrev Martin : > > From time to time we're trying to...
if it is still in HEAD I'd appreciate a PR!
ping @mrvanes what should we do about this?
I believe this was fixed with the content negotiation policy feature yes?
Thinking about how to implement this in the load pipeline it looks like it will be quite involved because of the complex error handling in that function. My thought is...