Bug 153428 - LayoutTests/http/tests/contentextensions/make-https.html has different results when running local web server on port 80
Summary: LayoutTests/http/tests/contentextensions/make-https.html has different result...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 148966
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-25 10:25 PST by Daniel Bates
Modified: 2016-01-25 12:33 PST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Bates 2016-01-25 10:25:16 PST
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.
Comment 1 Alexey Proskuryakov 2016-01-25 12:33:35 PST
I usually use port 7 when I want to hit a bounce.