This repository was archived by the owner on Jun 29, 2023. It is now read-only.
Add exact headers of a website request to API call #11
Conversation
This file contains hidden or 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
|
Thanks for your help! @paul0x1C and I played around a bit and just any user agent and an accept of application/json should work. For now, I'd like to use a user agent actually identify this project, seems like the fair thing to do. If they decide to actually block this user agent specifically, we might just do what you did and use the headers a browser would send. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Currently the API calls to MVG don't work as they banned the User-Agent.
This PR adds the exact same headers to the request as a current Chrome on macOS does to their API when using the website.
Closes #10