Tony, hello.
On 2008 Jan 18, at 15:38, Tony Linde wrote:
> Prob not much help but it renders ok in IE7 (which might be why others
> haven't complained)
It renders OK in Safari, too, which is why I didn't notice it.
Both these browsers are being naughty: RFC 2616 explicitly forbids browsers from sniffing the content type in those cases where a content-type header is present:
> Any HTTP/1.1 message containing an entity-body SHOULD include a
> Content-Type header field defining the media type of that body. If
> and only if the media type is not given by a Content-Type field,
> the
> recipient MAY attempt to guess the media type via inspection of its
> content and/or the name extension(s) of the URI used to identify
> the
> resource.
[Sect: 7.2.1]
I've sumbitted a Safari bug report.
Norman
[full-on standards lawyer]
-- Norman Gray : http://nxg.me.uk eurovotech.org : University of LeicesterReceived on 2008-01-18Z17:02:17