[hunchentoot-devel] Encoding problem

[Hans Hübner]

Nicolas,

I'd use Wireshark or another packet sniffing tool to capture the
request as it is exchanged between Apache and Hunchentoot.  In that
capture, it would be obvious what encoding would be used for the
headers.  Lacking that, you could also try setting
HUNCHENTOOT:*HEADER-STREAM* to *STANDARD-OUTPUT* or a stream of your
liking and inspect its contents.  Using an external sniffer would be
safer in that you'd know that nothing has processed the headers,
though.

Given that you already speculated at the wrong encoding used in an
environment variable that Apache uses, why don't you change that to
use proper RFC2047 encoding?

-Hans

On Thu, Oct 7, 2010 at 4:12 PM, Nicolas Neuss <neuss at kit.edu> wrote:
> Tomasz Lipski <tomek.lipski at gmail.com> writes:
>
>> On 7 October 2010 15:42, Nicolas Neuss <neuss at kit.edu> wrote:
>>> http://ruprecht.mathematik.uni-karlsruhe.de/misc/info.html
>>>
>>
>> Nicolas,
>>
>> I think that log from livehttpheaders Firefox plug-in/logging web
>> proxy would be more useful. With that, you can check what is sent from
>> the browser to the server directly
>> in the HTTP layer.
>>
>> Best regards,
>>
>> Tomek Lipski
>
> IIUC, that doesn't help.  The result is:
>
>    Antwort-Header - https://ruprecht.mathematik.uni-karlsruhe.de/sso/test-shibboleth
>
>    Date: Thu, 07 Oct 2010 14:09:45 GMT
>    Server: Hunchentoot 1.1.0
>    Content-Length: 4687
>    Content-Type: text/html; charset=utf-8
>    Via: 1.1 ruprecht.mathematik.uni-karlsruhe.de
>    Keep-Alive: timeout=15, max=100
>    Connection: Keep-Alive
>
> which shows that the encoding of the page shown in the browser should be
> correct.
>
> Thanks, Nicolas
>
> _______________________________________________
> tbnl-devel site list
> tbnl-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/tbnl-devel
>