From: Hashim Al-A. <ala...@gm...> - 2011-11-16 21:03:26
|
in the yaws.erl file special headers section: accumulate_header({connection, What}) -> DC = case What of "close" -> true; _ -> false end, this code will force the user to use lower case "close" but in my case I need "Close" with first caps and it is not mentioned in the documentation. you may change the code to: accumulate_header({connection, What}) -> DC = case What of "close" -> true; "Close" -> true; _ -> false end, and add that to the doc. thanks, P.S. I still have problems with the headers I need some examples |
From: Steve V. <vi...@ie...> - 2011-12-13 14:34:52
|
[Apologies for the slow response -- I've been traveling extensively, and Klacke's been traveling too.] On Wed, Nov 16, 2011 at 4:03 PM, Hashim Al-Adhami <ala...@gm...> wrote: > in the yaws.erl file special headers section: > > accumulate_header({connection, What}) -> > DC = case What of > "close" -> > true; > _ -> > false > end, > > this code will force the user to use lower case "close" but in my case > I need "Close" with first caps and it is not mentioned in the > documentation. I'm not sure "Close" is legal HTTP. I've looked through the HTTP 1.1 spec (RFC 2616) as well as the HTTPbis cleanup of the 1.1 spec, and in neither case does it say that field values are case-insensitive. Header names themselves are of course case-insensitive, but not necessarily their field values. I also looked to RFC 822 for guidance, which while not perfectly clear also seems to indicate that field values are case-sensitive. But if anyone can provide pointers to the standards that prove otherwise, please let me know. > you may change the code to: > > accumulate_header({connection, What}) -> > DC = case What of > "close" -> > true; > "Close" -> > true; > _ -> > false > end, > > and add that to the doc. Based on my reading of the specs, such a change would not be legal, as explained above. > P.S. I still have problems with the headers I need some examples If you could explain the problems you're having, I'm sure we could try to help. --steve |