[Plugin] request.path always None in v2.4.0rc7
#1035
Answered
by
abhinavsingh
softhub-software-development
asked this question in
Q&A
-
|
Since updating to v2.4.0.rc7, request.path is always set to None: |
Beta Was this translation helpful? Give feedback.
Answered by
abhinavsingh
Jan 21, 2022
Replies: 1 comment 9 replies
-
|
Please provide a concrete reproducible example. Example, whats the URL, how can we reproduce it using curl, or may be how does the raw request packet looks like? We have integration and unit test, something like this cannot be missed. Kindly double check your code. |
Beta Was this translation helpful? Give feedback.
9 replies
-
|
I would love to see some raw data to understand this problem. Here is how you folks can help:
|
Beta Was this translation helpful? Give feedback.
-
|
here is my curl here are outputs after uncomment codes above: plugin code : |
Beta Was this translation helpful? Give feedback.
-
|
So IIUC, you are getting path as |
Beta Was this translation helpful? Give feedback.
-
Yes ，so what's the problem? tks I found that when I request with http:
https:
|
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/abhinavsingh/proxy.py/blob/develop/proxy/http/parser/parser.py#L460 Path comes from here. Do read the related I'll also recommend to read https://github.com/abhinavsingh/proxy.py/blob/develop/tutorial/http_parser.ipynb which will explain inner working of parser class. |
Beta Was this translation helpful? Give feedback.
Answer selected by
abhinavsingh
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please provide a concrete reproducible example. Example, whats the URL, how can we reproduce it using curl, or may be how does the raw request packet looks like?
We have integration and unit test, something like this cannot be missed.
Kindly double check your code.