Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix: HTTP response with invalid headers doesn't throw error #28865 #29420

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

fix: HTTP response with invalid headers doesn't throw error #28865 #29420

wants to merge 2 commits into from
+205 −1

Commits on Apr 26, 2024

  1. fix: HTTP response with invalid headers doesn't throw error cypress-i… 

    …o#28865

When receiving the described HTTP response Cypress resets the headers.
This would cause the validateHeaderName method from node to be called
which would cause an error, since the headers where invalid.
Now Crypress verifies all the headers before reseting them,
discards invalid ones and sends a warning in the console
when debug module is on.
    @BernardoSousa03
    BernardoSousa03 committed Apr 26, 2024
    Configuration menu
    Copy the full SHA
    114fe47 View commit details
    Browse the repository at this point in the history

Commits on May 23, 2024

  1. fix: improved warning display to the command line 

    When cutting off invalid headers from the response the user
is informed of such headers in the command line
    @BernardoSousa03
    BernardoSousa03 committed May 23, 2024
    Configuration menu
    Copy the full SHA
    5dd3050 View commit details
    Browse the repository at this point in the history