ASA auth-proxy, secure-http-client and non-IE browsers

[cwinckless]

Good afternoon,

I'm working on using an ASA with secure-http-client to authenticate users outbound from a wireless network.

In testing I've run into issues with non-IE browsers displaying the raw HTML rather than being formatted by the browser. I've seen this with Mozilla and Firefox on Linux as well as Firefox on Windows.

Is this a known issue? And if so, is there a workaround.

-- Charlie

[ebreniz]

What do you mean by "formatted by the browser"? When I use secure-http-client, I see the text boxes asking for username and password on my IE. As I do not have other browsers, I do not know how it looks without formatting.

[mpelliott]

Hi Charlie,

This is really late replying but ive come accross this issue too. It's because the ASA/PIX only sends back 1 HTTP Header (Content-Length). As far as I know Firefox/mozilla browsers treat everything as Text, whereas IE treats everything as HTML. I was hoping someone would have an answer here but as they don't I guess there is currently no solution.. Surely not sending an HTTP/1.0 200 OK goes against the HTTP standards?? this seems like sloppy coding to me. Very unprofessional.

I could be wrong, but I can't see anything in the AAA config that would let me set extra headers...

Cheers,

Mark