From: Claes W. <kl...@hy...> - 2006-02-08 19:41:04
|
Dominique Boucher wrote: > 1 HTTP/1.1 200 OK > 2 Connection: Keep-Alive > 3 Server: Yaws/1.57 Yet Another Web Server > 4 DAV: 1 > 5 Date: Wed, 08 Feb 2006 15:11:44 GMT > 6 Last-Modified: Tue, 07 Feb 2006 02:37:07 GMT > 7 Etag: "1iNWUcAAAAA" > 8 Content-Length: 3005 > 9 Content-Type: text/css;charset= > The Content-Type header looks fishy. There is an (blush) undocumented feature whereby Yaws att compiletime can decide which charset should be used in the Content-Type header From mime_types_c.erl c() -> {ok, F} = file:open("mime.types", [read]), io:format("Compiling mime.types ... > mime_types.erl ~n", []), {ok, B} = file:read_file("charset.def"), case string:tokens(binary_to_list(B)," \r\n\t") of [] -> put(charset, []); [CharSet0] -> CharSet = string:strip(CharSet0, both, 10), put(charset, ";charset=" ++ CharSet); ..... So, if there is nonempty file called charset.def in the source directory, the contents of that file determines the charset. So, why do you get the ";charset=" part. ? What's the content of charset.def in your Yaws src dir ? I get: # curl -I http://yaws.hyber.org/stil.css HTTP/1.1 200 OK Server: Yaws/1.58 Yet Another Web Server Date: Wed, 08 Feb 2006 19:39:00 GMT Last-Modified: Tue, 12 Apr 2005 13:44:27 GMT Etag: "1UY+xsBBcOd" Content-Length: 1673 Content-Type: text/css Just a theory .... /klacke -- Claes Wikstrom -- Caps lock is nowhere and http://www.hyber.org -- everything is under control cellphone: +46 70 2097763 |