8000 Allow insecure requests · Issue #1 · fluofoxxo/outrun · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Allow insecure requests #1

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.

Sign up for GitHub

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

Jump to bottom
Closed
fluofoxxo opened this issue Aug 8, 2019 · 3 comments
Closed

Allow insecure requests #1

fluofoxxo opened this issue Aug 8, 2019 · 3 comments
Assignees
@fluofoxxo

Comments

@fluofoxxo
Copy link
Owner

Insecure requests are sent at least by /Battle/ requests. Sate the ability to utilize the data sent by these requests.

Notes:

  • secure = 0 when the request is insecure.
  • param is URL escaped when insecure.
  • key = nothing when insecure.
@fluofoxxo fluofoxxo mentioned this issue Aug 9, 2019
Open
@fluofoxxo
Copy link
Owner Author

Addendum: Does the game expect a secure request in response to the insecure request? Is the game flexible enough to handle insecure responses all the time, and likewise for secure responses?

@fluofoxxo fluofoxxo added good first issue Good for newcomers help wanted Extra attention is needed labels Aug 9, 2019
@fluofoxxo
Copy link
Owner Author

Addendum: Currently insecure requests cause panics due to the lack of an IV. Solve this.

@fluofoxxo fluofoxxo self-assigned this Aug 10, 2019
@fluofoxxo
Copy link
Owner Author

Tackling when I get a chance.

@fluofoxxo fluofoxxo removed good first issue Good for newcomers help wanted Extra attention is needed labels Aug 10, 2019
fluofoxxo pushed a commit that referenced this issue Oct 27, 2019
@Mtbcooler
Merge pull request #1 from Mtbcooler/Mtbcooler-patch-1
8147be3 
Added event IDs for event characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fluofoxxo fluofoxxo

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fluofoxxo
0