Skip to content
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

Decide what to do about links that don’t expose content-length or transfer-encoding #102

Open
tusbar opened this issue Sep 27, 2018 · 0 comments
Labels

Comments

@tusbar
Copy link
Contributor

tusbar commented Sep 27, 2018

Some links (like https://api.sandre.eaufrance.fr/referentiels/v1/dc.csv?compress=true) do not expose content-length or transfer-encoding headers, so hasBody from type-is returns false.

Such links do not respect http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.3, so it’d probably be best if they added the headers instead of us trying to figure if there is in fact a body.

//cc @jdesboeufs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant