- From: Chris Weber <chris@lookout.net>
- Date: Tue, 13 Nov 2012 17:05:50 -0800
- To: Philippe Le Hegaret <plh@w3.org>
- 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 11/13/2012 5:42 AM, Philippe Le Hegaret wrote: > Hi Chris, > >> A server with a wildcard DNS entry would be great. > > yes, we can look into that. > > We could reserve url-testing.w3c-test.org. Would that be good enough for > you? > Yes, I believe that plus the wildcard DNS entry ( *.url-testing.w3c-test.org ) would be all the infrastructure required for testing how the path and query components come across the wire, and for testing hostnames as well. So I suppose we could break this into two groups of test cases: 1. Testing the URL transmitted in a GET request 2. Testing the the hostname transmitted in the HTTP Host header For that second group, it would require the wildcard DNS entry to allow for any arbitrary subdomain requests to resolve via DNS, and subsequently be compared for the original and expected values from tests such as the following: foo.url-testing.w3c-test.org 天気の良い日.url-testing.w3c-test.org xn--nxasmq6b.url-testing.w3c-test.org fa\u00DF.url-testing.w3c-test.org Best regards, Chris
Received on Wednesday, 14 November 2012 01:06:12 UTC