diff options
author | bors-servo <lbergstrom+bors@mozilla.com> | 2016-03-18 00:31:24 +0530 |
---|---|---|
committer | bors-servo <lbergstrom+bors@mozilla.com> | 2016-03-18 00:31:24 +0530 |
commit | 0008c07dc343d911be042516b32c994fc18e3900 (patch) | |
tree | 142500f5f294807fd61f3f2226cb1d49ff5b94c4 /python/tidy.py | |
parent | 7a9dc577617b442ff0fe07eaa683207234c519ee (diff) | |
parent | 4ddf4e7bdcde769265acd23fa9dea28d2a05bb57 (diff) | |
download | servo-0008c07dc343d911be042516b32c994fc18e3900.tar.gz servo-0008c07dc343d911be042516b32c994fc18e3900.zip |
Auto merge of #10014 - saurvs:pr1, r=KiChjang
Update WebSocket blocked ports to match the Fetch spec
Adresses #9949.
This adds a function that tests whether a request should be blocked or not based on it's url's scheme and port. It also adds testing for port restriction to the `main_fetch` method. More info in https://github.com/whatwg/fetch/commit/eb07418c8383983a9887498e49a2e2e986d3c9f4.
@Ms2ger In https://github.com/whatwg/html/issues/841, @annevk proposes to remove port restrictions from websockets. Should we go ahead do that, given that the spec hasn't been changed yet?
<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/10014)
<!-- Reviewable:end -->
Diffstat (limited to 'python/tidy.py')
0 files changed, 0 insertions, 0 deletions