- From: Phil Archer <phil.archer@icra.org>
- Date: Mon, 18 Apr 2005 10:33:43 +0100
- To: "Dirk-Willem van Gulik" <dirkx@webweaving.org>
- Cc: "SWIG" <semantic-web@w3.org>
Thank you, adding the RDF MIME type to Apache's default configuration is very welcome news indeed. Can I just clear one thing up - the "extra module" I talked about was mod_headers that is (one of the ways) you can use to add and control custom HTTP Response Headers. If there's a way to add Link '</filename.rdf>; /="/"; rel="meta" type="application/rdf+xml";' to response headers without having to install any modules other than the default I'd be very pleased to hear about it! (Some use cases further require the Response Headers to be controlled using block directives as well). Thanks again Phil ----- Original Message ----- From: "Dirk-Willem van Gulik" <dirkx@webweaving.org> To: "Phil Archer" <phil.archer@icra.org> Cc: "SWIG" <semantic-web@w3.org> Sent: Monday, April 18, 2005 10:19 AM Subject: Re: Firewall problems with RDF MIME type? > > On Fri, 15 Apr 2005, Phil Archer wrote: > >> widely supported by servers in default configuration. Apache seems >> generally >> to send its default MIME type of plain/text and IIS seems to refuse to >> send > > Given that RFC 3870 / http://www.faqs.org/rfcs/rfc3870.html defines a > mime type - I'll get that added to the default apache config. > > Meanwhile you can do: > > AddType application/rdf+xml .rdf > > which does not require any special modules beyond the base/default setup. > >> (I've deliberately omitted the name of the firewall - suffice to say it's >> a >> good one form a good company). > > The majority of the content-inspecting firewall's use the same mime.types > file as Apache does. Having an RFC > > Dw. >
Received on Monday, 18 April 2005 09:38:39 UTC