Bug 153428
| Summary: | LayoutTests/http/tests/contentextensions/make-https.html has different results when running local web server on port 80 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Daniel Bates <dbates> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | achristensen, ap, chris, lforschler |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 148966 | ||
| Bug Blocks: | |||
Daniel Bates
When I ran all tests in LayoutTests/http/tests, the test LayoutTests/http/tests/contentextensions/make-https.html (added with the patch for bug #148966) failed with different results because I am running a local web server on port 80 and the test tries to load <http://127.0.0.1:80/nope>. It would be good if our HTTP tests only made use of ports opened by run-webkit-tests/run-webkit-httpd to avoid being affected by other web servers that may be running on the machine. I'm unclear if it is straightforward to achieve the same test coverage provided by LayoutTests/http/tests/contentextensions/make-https.html without actually trying to connect to a local web server running on ports 80, 443, and 1443.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
I usually use port 7 when I want to hit a bounce.