-
Notifications
You must be signed in to change notification settings - Fork 9
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
Parsing Accept header of newer Chrome fails #56
Comments
@AdamChlupacek Thank you! And no worries about delays. |
@eikek The snapshot is now released with this change, we are not doing full release yet as there is not enough changes from the last version yet, be free to use 0.3.18-SNAPSHOT, it is stable. We are using it in production as well. |
Thanks @AdamChlupacek ; I now created a workaround such that all headers that failed to parse are ignored (mapped to empty values). For my apps that is just fine. |
Hi,
from some Android device running Chrome 73, the following Accept header is sent
The parser fails on the last
v=
part, saying expecting aq=
instead:I don't know what
v=
means. The user agent string isMozilla/5.0 (Linux; Android 7.0; Lenovo TB-7304F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.90 Safari/537.36
and I'm usingprotocol-http
version 0.3.12.The text was updated successfully, but these errors were encountered: