Darío Kondratiuk
|
b9b6ca1825
|
fix(network): be able to remove headers using request.continue (#4797)
I think this was a regression caused here https://github.com/GoogleChrome/puppeteer/pull/4265/files#diff-d2ac7cb061b0c51644d0a5d6140e3a32R446
Fix #4743
|
2019-08-05 15:26:17 -07:00 |
|
Joel Einbinder
|
f2056a8e25
|
fix(test): enable redirect inside sync XHR test (#4805)
The underlying bug appears to have been fixed. Test works.
|
2019-08-05 15:19:34 -07:00 |
|
Andrey Lushnikov
|
8df0b3ec3b
|
fix(network): allow fulfilling requests with status code 422 (#4566)
Migration onto fetch domain (2265974ce5)
changed the way we generate status texts: instead of relying on build-in
list of statuses, we tried to rely upon the [Chromium implementation](https://cs.chromium.org/chromium/src/net/http/http_status_code_list.h?sq=package:chromium&g=0).
Puppeteer's list is much more exhaustive - let's keep it.
Fix #4454
|
2019-06-10 17:39:58 -07:00 |
|
Andrey Lushnikov
|
15804d111a
|
test: remove debug console.log (#4522)
|
2019-06-04 16:27:36 -07:00 |
|
Andrey Lushnikov
|
d221c02c13
|
test: add test to verify fetching of dataURL requests (#4233)
|
2019-05-31 17:11:55 -07:00 |
|
Jake Causon
|
90a1032300
|
fix(network): stringify response headers for intercepted requests (#4436)
Stringifying the headers was the behaviour before v1.15
References #4379
|
2019-05-20 11:05:32 +03:00 |
|
Andrey Lushnikov
|
f3db28c94b
|
test: add failing test for request interception with sync XHRs (#4350)
`Network.requestWillBeSent` is not issued for the redirect inside
sync XHRs.
References #4337.
|
2019-04-26 16:28:15 -07:00 |
|
Andrey Lushnikov
|
770411be9d
|
test: verify overriding postdata and method on navigation (#4317)
References #4309
|
2019-04-19 18:22:30 -07:00 |
|
Andrey Lushnikov
|
8f8e77492d
|
test: split out request interception tests (#4278)
|
2019-04-11 21:33:01 -04:00 |
|