Can't show correct HTTP Response Code when access https URL through proxy
Categories
(DevTools :: Netmonitor, defect)
Tracking
(Not tracked)
People
(Reporter: yaozhen_guo, Unassigned)
Details
Attachments
(6 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36
Steps to reproduce:
Access https url through Proxy.
Actual results:
From screen-shot we can find http code is 200, it is connect http proxy response code, but real http code should 302, because this is response has location header. And Chrome developer tool can show the real 302 http code.
Expected results:
It needs to show real http code 302.
Updated•5 years ago
|
Comment 1•5 years ago
|
||
@yaozg: thanks for the report!
Can you please provide detailed instructions about how you are setting the proxy, thanks!
Honza
I used CCProxy as proxy tool, my firefox proxy's set to my CCproxy IP and port, please refer attached file.
If access any https website, and let the site response http code 302. then you can find the issue.
Comment 4•5 years ago
|
||
The priority flag is not set for this bug.
:Honza, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 5•5 years ago
|
||
Hubert, can you please try to reproduce this one?
Thanks,
Honza
Comment 6•4 years ago
•
|
||
Sorry for the delay in replying.
@yaozg i am finding difficult to reproduce atm.
I am testing on a MAC and it looks like CCProxy only exists for windows.
I've tried using Proxifier and Proxyman on my mac but can seem to reproduce.
Can you pls provide a simple STR?
With a screencast also if possible?
Updated•4 years ago
|
Reporter | ||
Comment 10•4 years ago
|
||
Reporter | ||
Comment 11•4 years ago
|
||
What is 'STR'? If you need a reproducible website?
you can try this URL.
https://idcs-04f9e22d78f94aa9908b1bbd16471b02.identity.oraclecloud.com/ui/v1/adminconsole
I have attached Firefox and Chrome screen-shot and har file, please refer.
Comment 12•4 years ago
|
||
Thanks for the details @yaozg.
Looks like we have a duplicate with Bug 833774 which has made progress.
Description
•