- From: Philippe Le Hegaret <plh@w3.org>
- Date: Tue, 13 Nov 2012 08:42:42 -0500
- To: Chris Weber <chris@lookout.net>
- Cc: Larry Masinter <masinter@adobe.com>, "julian.reschke@gmx.de" <julian.reschke@gmx.de>, "public-test-infra@w3.org" <public-test-infra@w3.org>
On Mon, 2012-11-12 at 23:10 -0800, Chris Weber wrote: > On 11/12/2012 8:13 AM, Larry Masinter wrote: > > I think I heard from Philippe that perhaps W3C could help set up a > > server (with wildcard DNS entry) for testing? Or is there some other > > kind of instrumentation we could use in the browser to test URL > > parsing? Hi Chris, we have so far available on port 80, 81, 81, and 83: http://w3c-test.org/ http://www.w3c-test.org/ http://www1.w3c-test.org/ http://www2.w3c-test.org/ http://天気の良い日.w3c-test.org/ http://élève.w3c-test.org/ In addition we have: https://www.w3c-test.org/ > A server with a wildcard DNS entry would be great. yes, we can look into that. > It would be the most > transparent way I can think of to test how the parsed URL hits the wire. > > But we might need a dedicated domain name to use as well, e.g. > w3c-url-testing.com, because the server would need to handle all > arbitrary incoming requests produced by the test cases, and we wouldn't > want them interfering with the existing test domain, e.g.: > > GET /foo/bar/1?2=3 > GET /bar/foo/ > GET /c%7C//foo/bar.html > GET /foo%2%C3%82%C2%A9zbar > ... We could reserve url-testing.w3c-test.org. Would that be good enough for you? Philippe
Received on Tuesday, 13 November 2012 13:42:56 UTC