From: Dominique B. <dom...@nu...> - 2006-02-08 20:22:16
|
Claes, > > 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 > [...] > 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 ? That's it! The charset.def contained two characters, whose codes are 0 and 12. This happens when the shell command % echo > somefile is run on cygwin. Removing the file and recompiling fixed the problem. So I guess the Makefile in src/ should be patched to test for an empty DEFAULT_CHARSET. In this case, the charset.def file should not be generated. Thanks a LOT! Dominique |