Enforce User-Agent header to be set. Fixes #54 #55
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Just dont set the header at all and it will be present. |
|
Just tried it: If the ua-header is not set explicitly, "Go-http-client/1.1" is used. But in this case, I get the 404 error again. Looks like Nissan is blocking some user agents. |
|
…or thats the login error now? |
|
Why don't you try it yourself? The behaviour is reproducible. I would not be suprised if they would try to block "non-official" requests. Ideally, we would set the user agent identical to the official app. Does anyone know what is set there? |
I did. Doesn't work for me. That's why I've asked
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A User-Agent header is required for the login. Fixes #54.