-
Notifications
You must be signed in to change notification settings - Fork 42
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
fix: capture redirected requests in waterfall #180
fix: capture redirected requests in waterfall #180
Conversation
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found a potential issue. Also, can we add a unit test around this logic?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Docker build issue is fixed by #179 |
requestId
which was overriding the original request with the redirected request. As a result the redirected requests was simply not shown in the waterfall.requestId
and simply mimic the usual flow fromrequestSent
->responseReceived
->LoadingFinished
by using the redirected response which is available as part of theevent.redirectedResponse
data.Check the below events for a sample website which goes from HTTP -> HTTPS and how 301 works.
Verification
Timings for
http://vigneshh.in
-> NO SSL timing as its HTTP endpointTimings for
https://vigneshh.in