httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Lord" <mailing-li...@msdi.ca>
Subject [users@httpd] Packet debugging when using mod_ssl
Date Wed, 18 Jun 2008 14:48:00 GMT
Hi,

I am dealing with a connexion problem from a custom web browser.

For some reason, one particular user from the custom web browser is getting
an error 400 (Bad Request) from Apache on a specific page requested by POST.

I've did a lot of research and can't find what's wrong... I would like to
see the actual packets for the request to see what's in there to try to
diagnose the product further... The problem is that the connexion is ssl
encrypted with mod_SSL...

A packet analyser gave me the encrypted content so I am not able to analyse
it.

I found out about mod_log_forensic which dump the request to log file, but I
am not sure if I can trust the results. Log forensic shows a get request
instead of a post and it's very basic
"
+212e:485861ea:0|GET /
-212e:485861ea:0
"

In there, I expect to see a post, not a get, the host, the referrer, the
"Accept", etc but I see only this...

That's why I presume that the request is so bad apache doesn't log it
correctly using mod_log_forensic...

Is there a way to actually "dump" the content of the request after being
decrypted by mod_ssl but before it is analysed for processing ?

Or can anyone suggest me a way to debug this further ?

Thanks in advance




---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message