Hello everyone!

 I started to use pound for routing wap requests and discovered that it
dropped some headers produced by the operator's wap gateway.

 I've seen these two special header being rejected in the logs:

13-profile: <url of an xml file describing the mobile device
capabilities>

X-WAP.TOD: 00

 I don't care for the second one as I don't know what it means but
the first one is very handy.

 After looking at the code and RFC 2616 I discovered that pound did not
accept the full set of valid headers. Pound only accept headers with
a field-name starting with a letter and followed by any number of letters,
digits, underscores or hyphens. But according to the RFC 2616 a valid
field-name is made of at least one ASCII character except the control
characters (0 - 31 and 127) and the seperators which are:

       separators     = "(" | ")" | "<" | ">" | "(at)"
                      | "," | ";" | ":" | "\" | <">
                      | "/" | "[" | "]" | "?" | "="
                      | "{" | "}" | SP | HT

 So I made the attached patch which remove the constraint on the first char
being a letter and add these chars in the allowed set: .!#%&'`^~$*+|

Cheers,

                Olivier
[...]

I think you forgot to attach the patch :)

... John 
[...]

On Thursday 21 October 2004 16.42, Olivier Dormond wrote:[...]

OK - I added it to the main branch, but given my misgivings about this I put 
it under conditional compilation. You'll have to ./configure --enable-unsafe 
to activate it.

New -current available on the Pound page - as always try it and let us
know.[...]