- From: Tobie Langel <tobie@w3.org>
- Date: Thu, 18 Jul 2013 14:43:00 +0200
- To: Ms2ger <ms2ger@gmail.com>
- Cc: public-test-infra <public-test-infra@w3.org>, Richard Ishida <ishida@w3.org>, duerst@it.aoyama.ac.jp, Anne van Kesteren <annevk@annevk.nl>, Phillips, Addison <addison@lab126.com>
On Thursday, July 18, 2013 at 2:32 PM, Ms2ger wrote: > On 07/18/2013 01:08 PM, Tobie Langel wrote: > > Hi all, > > > > I've received a number of requests for .htaccess support or the ability to write server-side code in order to be able to set HTTP headers. > > > > Supporting .htaccess ties us to Apache, which makes our test suite less portable. And although there are valid use cases for writing server-side code (which will of course be supported), setting HTTP headers hardly seems to be one of them. > > > > Instead I suggest we agree on the following convention to set HTTP headers for specific files: just add those headers in a file with the same filename and a .headers extensions. > > > > So for example, specifying a specific charset for the `the-input-byte-stream-001.html` file would consist in adding a file named `the-input-byte-stream-001.headers` in the same directory with the following content: > > > > Content-Type: text/html; charset=iso-8859-15 > > > > These directives would be picked up by the server whenever a file was requested and would override any defaults. > > > > Thoughts? > Completely agree; that's what I filed bug 13875 [1] for two years ago. > > For integration at Mozilla, using foo.html^headers^ rather than > foo.html.headers would be slightly easier. Thanks for the pointer. <3 prior art. But "^headers^" really!? --tobie
Received on Thursday, 18 July 2013 12:43:10 UTC