I do wonder why there aren't any newlines. Was that lost in the paste, or is that really what Bauk produces as a response?
If my spec-memory is correct, HTTP defines a newline as a CR LF, there's supposed to be one after each header, and the request ends with a double newline. I can't see that in the paste. It's possible, that Fossil, like Chrome is less forgiving of bogus input? (I can hardly blame it, Accept and cookie-specific headers are already difficult enough to parse without having to guess where they end...) cheers lvh _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
