The displayed HTTPS response status / remote address comes from proxy, not from web server
Categories
(DevTools :: Netmonitor, defect, P2)
Tracking
(Not tracked)
People
(Reporter: freddy, Assigned: bomsy, NeedInfo)
References
(Blocks 1 open bug)
Details
(Whiteboard: [polish-backlog])
Attachments
(3 files)
Reporter | ||
Comment 1•12 years ago
|
||
Comment 2•12 years ago
|
||
Updated•12 years ago
|
Reporter | ||
Comment 3•12 years ago
|
||
Comment 4•12 years ago
|
||
Reporter | ||
Comment 7•12 years ago
|
||
Comment 8•12 years ago
|
||
Reporter | ||
Comment 9•12 years ago
|
||
Comment 10•12 years ago
|
||
Updated•12 years ago
|
Comment 11•10 years ago
|
||
Comment 15•8 years ago
|
||
Updated•6 years ago
|
Comment 16•6 years ago
|
||
Reporter | ||
Comment 17•5 years ago
|
||
Honza, do you think we could revisit prioritization here?
Comment 18•5 years ago
|
||
Comment 19•5 years ago
|
||
Frederik, I attached a test patch that seems to be fixing the problem on my machine.
I also pushed it to try:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=35c7f4fa7d2b5e4bc8282dcc4d034cbc5a16508c&selectedJob=254907619
(win, linux, mac builds available)
Can you please test it and let me know if the patch fixes the issue for you?
Thanks,
Honza
Reporter | ||
Comment 20•5 years ago
|
||
Thank you so much for taking a stab at this!
Unfortunately, instead of showing "200 Connection Established" it now shows "200 200", see attached screenshot
Comment 21•5 years ago
|
||
(In reply to Frederik Braun [:freddyb] (PTO July 8th to 29th) from comment #20)
Unfortunately, instead of showing "200 Connection Established" it now shows "200 200", see attached screenshot
I fixed a typo in the patch, can you please try again?
Honza
Reporter | ||
Comment 22•5 years ago
|
||
Sorry. I won't find the time today and I'm heading out for a few weeks. Can you find someone else to test please? I've been using https://github.com/zaproxy/zaproxy/releases/tag/v2.8.0 but any proxy would work :-)
Comment 23•5 years ago
|
||
Nicolas, would you have time to test my patch here?
Thanks,
Honza
Comment 24•5 years ago
|
||
sure!
Comment 25•5 years ago
|
||
Comment 26•5 years ago
|
||
So I was able to reproduce the issue using OWASP ZAP (doing a fetch to a non-existent endpoint would show a 200 status)
I'm seeing a fix with your patch, but only for the netmonitor (the console still displays a 200, I guess we are not re-rendering something?)
Comment 27•5 years ago
|
||
Thanks for testing this Nicolas!
Patch updated, the Console panel should be fixed now.
Honza
Comment 28•5 years ago
|
||
yes, works fine in the console as well with the latest patch :) Thanks!
Comment 29•5 years ago
|
||
Some notes:
- HAR export needs to be tested (the true status needs to be exported)
- Console panel doesn't show the status+text within the expanded body
- There should be a test
Honza
Comment 31•4 years ago
|
||
May we fix it?
Comment 32•4 years ago
|
||
(In reply to yaozg from comment #31)
May we fix it?
Sorry, this bug is already assigned.
But, you might try to check some of our good-first-bugs
https://bugzilla.mozilla.org/buglist.cgi?keywords=good-first-bug&keywords_type=allwords&resolution=---&query_format=advanced&bug_status=NEW&component=Netmonitor&product=DevTools&list_id=15230961
Honza
Assignee | ||
Comment 34•3 years ago
|
||
This should be fixed by Bug 1734573. i'll confirm and close
Updated•2 years ago
|
Comment 35•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates.
:bomsy, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Comment 36•2 years ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Description
•