New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix resource proxy encoding errors #896
Conversation
…ssues with chunked responses. Improve overall performance and error reporting.
@joetsoi Hey, I added a commit to fix issues with servers that do not support HEAD requests. |
@joetsoi I'm keen into get this into 2.0.1 can you review and merge at some point next week if you are happy? |
@domoritz This was flagged as 2.0.1 but the whole PR is not compatible with it as it was branched afterwards (eg tests in 2.0.1 don't use httpretty). If you can provide a 2.0.1 fix in a new PR I'll merge it, otherwise it would have to be 2.1 only. |
@amercader I can copy the changes to the resource proxy but not the tests to keep it compatible with 2.0 and send a pull request tomorrow. |
@amercader Fixes for 2.0 in #980. |
Conflicts: ckan/tests/test_coding_standards.py
Some resources cannot be proxied because of encoding issues. For example http://www.berlin.de/ba-lichtenberg/buergerservice/familie/tagespflege/index.php/index/all.json?q=.
The error in Firefox:
Content Encoding Error
In Chrome:
Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error.
In curl:
url: (56) Problem (2) in the Chunked-Encoded data