addaleax · GitHub

From the issue:
> Some servers deviate from HTTP spec enougth that Node.js can't
> communicate with them, but "work" when `--insecure-http-parser`
> is enabled globally. It would be useful to be able to use this
> mode, as a client, only when connecting to known bad servers.
This is largely equivalent to nodejs#31446
in terms of code changes.
Fixes: nodejs#31440
Refs: nodejs#31446

@addaleax added http

Issues or PRs related to the http subsystem.

semver-minor

PRs that contain new features and should be released in the next minor version.

labels

Jan 21, 2020

@addaleax 

…er-server

sam-github

…er-server

@addaleax addaleax added the author ready

PRs that have at least one approval, no pending requests for changes, and a CI started.

label

Jan 22, 2020

sam-github

Trott

Trott

…er-server
Co-Authored-By: Rich Trott <rtrott@gmail.com>

addaleax added a commit that referenced this pull request

Jan 24, 2020 
From the issue:
> Some servers deviate from HTTP spec enougth that Node.js can't
> communicate with them, but "work" when `--insecure-http-parser`
> is enabled globally. It would be useful to be able to use this
> mode, as a client, only when connecting to known bad servers.
This is largely equivalent to #31446
in terms of code changes.
Fixes: #31440
Refs: #31446
PR-URL: #31448
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>

@addaleax

addaleax added a commit to sam-github/node that referenced this pull request

Jan 24, 2020 
From the issue:
> Some servers deviate from HTTP spec enougth that Node.js can't
> communicate with them, but "work" when `--insecure-http-parser`
> is enabled globally. It would be useful to be able to use this
> mode, as a client, only when connecting to known bad servers.
This is largely equivalent to nodejs#31446
in terms of code changes.
Fixes: nodejs#31440
Refs: nodejs#31446
PR-URL: nodejs#31448
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>

Closed

4 tasks

addaleax added a commit to addaleax/node that referenced this pull request

Jan 24, 2020 
From the issue:
> Some servers deviate from HTTP spec enougth that Node.js can't
> communicate with them, but "work" when `--insecure-http-parser`
> is enabled globally. It would be useful to be able to use this
> mode, as a client, only when connecting to known bad servers.
This is largely equivalent to nodejs#31446
in terms of code changes.
Fixes: nodejs#31440
Refs: nodejs#31446
PR-URL: nodejs#31448
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>

zsw007 added a commit to ibmruntimes/node that referenced this pull request

Feb 11, 2020 
Backport  7fc5656 
Original commit message:
    From the issue:
    > Some servers deviate from HTTP spec enougth that Node.js can't
    > communicate with them, but "work" when `--insecure-http-parser`
    > is enabled globally. It would be useful to be able to use this
    > mode, as a client, only when connecting to known bad servers.
    This is largely equivalent to
    nodejs/node#31446 in terms of code changes.
    Fixes: nodejs/node#31440
    Refs: nodejs/node#31446
    Backport-PR-URL: nodejs/node#31500
    PR-URL: nodejs/node#31448
    Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
    Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
    Reviewed-By: James M Snell <jasnell@gmail.com>
    Reviewed-By: Rich Trott <rtrott@gmail.com>

zsw007 added a commit to ibmruntimes/node that referenced this pull request

Feb 12, 2020 
Backport  7fc5656 
Original commit message:
    From the issue:
    > Some servers deviate from HTTP spec enougth that Node.js can't
    > communicate with them, but "work" when `--insecure-http-parser`
    > is enabled globally. It would be useful to be able to use this
    > mode, as a client, only when connecting to known bad servers.
    This is largely equivalent to
    nodejs/node#31446 in terms of code changes.
    Fixes: nodejs/node#31440
    Refs: nodejs/node#31446
    Backport-PR-URL: nodejs/node#31500
    PR-URL: nodejs/node#31448
    Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
    Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
    Reviewed-By: James M Snell <jasnell@gmail.com>
    Reviewed-By: Rich Trott <rtrott@gmail.com>

zsw007 added a commit to ibmruntimes/node that referenced this pull request

Feb 12, 2020 
Backport  7fc5656 
Original commit message:
    From the issue:
    > Some servers deviate from HTTP spec enougth that Node.js can't
    > communicate with them, but "work" when `--insecure-http-parser`
    > is enabled globally. It would be useful to be able to use this
    > mode, as a client, only when connecting to known bad servers.
    This is largely equivalent to
    nodejs/node#31446 in terms of code changes.
    Fixes: nodejs/node#31440
    Refs: nodejs/node#31446
    Backport-PR-URL: nodejs/node#31500
    PR-URL: nodejs/node#31448
    Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
    Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
    Reviewed-By: James M Snell <jasnell@gmail.com>
    Reviewed-By: Rich Trott <rtrott@gmail.com>

Read the original on github.com ↗