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
Can not return {header, {accept_ranges, "bytes"}} #352
Comments
The
See the yaws_api(5) man page or the yaws pdf documentation, section 7.6 for a list of headers for which Yaws allows atom names. |
|
Correct, which is why it'll work fine if you specify it as a string. And even if I add it to |
But it is a bit confusing though where you can specify the atom |
Thanks, @vinoski. |
Hi @vinoski I just discovered something unusual after the change. The following no longer outputs the
|
Add a new unit test for accept_ranges to return both atom form and string form for the header and verify the presence of "Accept-Ranges" in the response.
Thanks, this was my mistake. Fixed on master now, and with a new unit test. |
Thanks for the fix. |
Add special treatment for the atom accept_ranges in output header specifications for setting the standard "Accept-Ranges" header. Add accept_ranges to the documentation.
Add a new unit test for accept_ranges to return both atom form and string form for the header and verify the presence of "Accept-Ranges" in the response.
Returning
{header, {accept_ranges, "bytes"}}
fromout/1
causes a crash:The text was updated successfully, but these errors were encountered: