-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
request.rel_url didn't return fragment (by the server-aiohttp) #3340
Comments
GitMate.io thinks the contributor most likely able to help you is @asvetlov. Possibly related issues are #2920 (AIOHttp failing after some requests), #206 (SSL issue with aiohttp.request), #127 (verify_ssl for aiohttp.request), #3274 (1K Request can't be finished in a simultaneous way in aiohttp), and #1541 (Aiohttp.web server timeout on long requests.). |
The fragment is for client-side only. |
Hello, I am using python 3.7 with aiohttp 3.5.1 I am not reading the fragment to return it to the a client. But I need it to verify the client is who they say they are. See https://aiohttp.readthedocs.io/en/stable/web_reference.html#aiohttp.web.BaseRequest.rel_url for the docs that state fragment should be present in self.request.rel_url |
Long story short
in the aiohttp-server should exist request.real_url like in client
in the request (request.rel_url) received by the server, the fragment is gone
Expected behaviour
Actual behaviour
request.rel_url == "/authorize"
Steps to reproduce
Server code:
client code:
Your environment
server
aiohttp==3.4.4
python 3.7
The text was updated successfully, but these errors were encountered: