Re: POST problem
Ok, then I've to check now POST+keepalive+redirection, too. What a nice thing
that the HTTP protocol makes has such a lot of esoteric combinations
possibleI'll investigate when I find time.
Just FYI, i've also come across the POST+keepalive+redirection problem. I think
i'm right in saying it's still a problem because i can't see it in the changes
for 2.2.6.
I've also come across the POST problem.
And I think that I found the hint of the problem.
/contact/index.html is the html file with form.
And I wrote in the form,then I click the submit button.
14:08:07 log is strange.
[debug] OpenSSL: write 23/23 bytes to BIO#00140880 [mem: 00155638] (BIO dump follows)
Why is the first line of 14:08:07 "write"?
access_log:
XXX.XXX.XXX.XX - - [26/Mar/1999:14:07:51 +0900] "GET /contact/index.html HTTP/1.0" 304
-
XXX.XXX.XXX.XX - - [26/Mar/1999:14:07:51 +0900] "GET /icon/inquiryhead.gif HTTP/1.0"
304 -
ssl_engine_log (debug):
[26/Mar/1999 14:07:51] [debug] OpenSSL: read 419/18437 bytes from BIO#00140880 [mem:
00150E28] (BIO dump follows)
+-+
| : 17 03 01 01 9e 9f 62 78-e9 92 1b 1c 5d 27 77 51 ..bx]'wQ |
| 0010: ca c9 60 10 6b bd 55 03-54 9d 44 90 2f 82 00 31 ..`.k.U.T.D./..1 |
| 0020: 21 a0 cd 5d c4 30 35 b6-10 45 39 69 5e d5 be 4e !..].05..E9i^..N |
| 0030: ac 84 ac d8 6b 8c 87 e3-4a f4 79 5f 4d 77 fb 22 k...J.y_Mw." |
| 0040: c6 5b d6 8a bd af 37 55-55 8e a4 1f ce 7a ad a9 .[7UUz.. |
| 0050: 9a 0a 27 a6 f7 ca ff a1-c2 9a 16 b5 d7 37 cd fa ..'..7.. |
| 0060: 65 ff 0c e7 17 69 42 c1-d5 f8 0a 4d b0 3f 9d 56 eiBM.?.V |
| 0070: 8a 81 5b f2 80 ab a5 80-18 23 58 80 99 f7 0c a7 ..[..#X. |
| 0080: 1a 1e d0 a5 c3 1c 17 a9-88 d2 31 ed f1 68 5d 35 ..1..h]5 |
| 0090: 7a 97 28 92 48 c3 b8 9a-4d cb 4f 5b a7 c5 c1 ca z.(.H...M.O[ |
| 00a0: 51 0f e9 55 01 35 d3 8b-9e e8 ac 14 05 25 4b f5 Q..U.5...%K. |
| 00b0: 6f e1 bb 77 6d 62 79 6d-aa 70 57 a7 73 dc f9 9b o..wmbym.pW.s... |
| 00c0: cd 3c e5 5e 40 d7 45 b3-21 70 db 7e 7c 13 3e 87 ..^@.E.!p.~|.. |
| 00d0: db 23 d8 f3 c5 6c 7d 0f-4d 87 ce 35 46 be 0a c9 .#...l}.M..5F... |
| 00e0: 07 41 f7 b6 90 c5 5f 74-2f f6 16 2a 86 08 23 44 .A_t/..*..#D |
| 00f0: fc 9b a8 91 aa 0a fc f4-fb 71 7b 35 3a e8 83 ae .q{5:... |
| 0100: ac 7e c8 79 38 76 e9 e7-9b 98 02 45 b5 0b c7 33 .~.y8v.E...3 |
| 0110: 5c 05 59 48 b3 9a 2a 96-53 da 58 a4 44 17 13 7f \.YH..*.S.X.D... |
| 0120: 4a d7 d3 52 bb 14 40 f5-43 69 db cc 3e 9f 7e 06 J..R..@.Ci...~. |
| 0130: 9e 86 f5 a3 7a 83 f6 bd-5d 3c 05 e7 4c fc 6c 9b z...]..L.l. |
| 0140: 58 fd 8a 76 c5 dc b0 1b-c6 f0 8e bd 08 df c4 33 X..v...3 |
| 0150: 84 fc 87 70 a9 5e 3f 1c-1c 96 2c 4a 3f 07 03 79 ...p.^?...,J?..y |
| 0160: 30 ac c1 e3 99 08 20 f8-b2 83 d5 79 d3 3a ec d3 0. y.:.. |
| 0170: 2b 88 35 84 8c e1 ad d3-6a 38 92 8d da e3 98 2a +.5.j8.* |
| 0180: 44 b3 88 fd 9b 4f dc 4a-bd 04 38 ad 1c 98 22 45 DO.J..8..."E |
| 0190: a5 5c 45 f3 37 e1 2a 9d-31 94 1d 96 67 02 90 93 .\E.7.*.1...g... |
| 01a0: 4a db c0 J.. |
+-+
[26/Mar/1999 14:07:51] [info] Subsequent (No.4) HTTPS request received for child 1
(server xxx.xxx.xxx.xxx.xxx.xxx:443
)
[26/Mar/1999 14:07:51] [debug] OpenSSL: write 229/229 bytes to BIO#00140880 [mem:
00155638] (BIO dump follows)
+-+
| : 17 03 01 00 e0 2d 5c c4-86 16 85 87 8e 94 17 4b .-\K |
| 0010: a2 d9 35 e6 7d 83 8f 2f-83 5f 5b de 01 ee 9a 3f ..5.}../._[? |
| 0020: 46 48 2f a2 f2 cf d6 ea-e4 24 e7 8f 53 58 65 19 FH/..$..SXe. |
| 0030: d2 a0 f8 66 93 ae ac f2-07 2a 4b e4 1d c8 a1 97 ...f.*K. |
| 0040: 77 dd ce 0f c0 0c 94 fd-88 4b 82 4f b2 6c 37 49 wK.O.l7I |
| 0050: 65 01 73 e4 70 ba 79 ad-99 e0 8e 6d 0c 11 5a 9f e.s.p.ym..Z. |
| 0060: d5 da 6a 79 e3 c0 17 30-00 60 8c 3d a7 79 27 53 ..jy...0.`.=.y'S |
| 0070: 31 5c c4 0c ac 7c d7 26-19 a7 4f df f9 c3 09 7f 1\...|...O. |
| 0080: ea 9f 9d 68 ab 68 0d ec-dd fb 66 fb eb df 3b fe ...h.hf...;. |
| 0090: d3 d1 e0 8a 9c 83 78 98-b1 a8 b2 5b ee 20 6c e3 ..x[. l. |
| 00a0: d7 a2 94 73 d3 b1 17 c5-ef 61 4e 38 89 f2 8f 1b ...s.aN8 |
| 00b0: 18 9c f0 cf ab 8c cb b1-3a dd 43 8d ca 47 ed 72 :.C..G.r |
| 00c0: 5a 2d e5 3e 25 d7 0c c5-e6 78 35 b9 c1 02 f2 f3 Z-.%x5. |
| 00d0: 37 b6 7c eb 73 ee 77 33-04 2a c8 1d 1e 2e 3b 6e 7.|.s.w3.*;n |
| 00e0: 69 c4 16 14 c9 i|
+-+
[26/Mar/1999 14:07:51] [debug] OpenSSL: read 354/18437 bytes from BIO#00140880 [mem:
00154E50] (BIO dump follows)
+-+
| : 17 03 01 01 5d 48
Re: POST problem
Ralf S. Engelschall wrote: Ok, then I've to check now POST+keepalive+redirection, too. What a nice thing that the HTTP protocol makes has such a lot of esoteric combinations possibleI'll investigate when I find time. Just FYI, i've also come across the POST+keepalive+redirection problem. I think i'm right in saying it's still a problem because i can't see it in the changes for 2.2.6. thanks, Tony. -- - Tony Locke [EMAIL PROTECTED] Programmer, Open World Limited - __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: POST problem
On Sun, Mar 21, 1999, [EMAIL PROTECTED] wrote: I just did the following: cd apache_1.3.4 make clean cd ../mod_ssl-2.2.5-1.3.4 ./configure ... cd ../apache_1.3.4 ./configure ... make make install which would seem to COMPLETELY rebuild the apache and mod_ssl source trees, and I'm still having the POST problem, using mod_ssl with DSO. Hmmm... I've yesterday evening tried it again myself with a little POST cgi-script and all worked fine. So, you've to give me more details on your particular "POST problem" or I cannot help you. Perhaps it's something different this time. What exact URLs you request, what scripts/pages are on the filesystem and how are they configured? BTW, Apache doesn't allow POSTs to all things per default and Netscape doesn't like Apache's non-200/OK response in these cases. So, are you sure your "POST problem" works at least with plain HTTP? I have four scripts that I call using HTTPS. Two are C programs, one is a PHP3.0.7 script, and one is a shell script. All of these scripts work over HTTP with POST. All work over HTTPS with GET. One of the C programs and the shell script work over HTTPS with POST. The other C program and the PHP script do not. The scripts that work both do some processing and send output to the browser. The scripts that don't work do some processing then send a "Location: " header to send to another page. The problem appears to be in the redirection, then. This is the error I get: "An I/O error occured during security authorization. Please try your connection again" I'm using: Apache 1.3.4 mod_ssl 2.2.5-1.3.4 openssl 0.9.1c (upgrading shortly) PHP 3.0.7 Netscape 4.07 Linux 2.0.36 glibc 2.0.7 -mike Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: POST problem
On Mon, Mar 22, 1999, [EMAIL PROTECTED] wrote: [...] I have four scripts that I call using HTTPS. Two are C programs, one is a PHP3.0.7 script, and one is a shell script. All of these scripts work over HTTP with POST. All work over HTTPS with GET. One of the C programs and the shell script work over HTTPS with POST. The other C program and the PHP script do not. The scripts that work both do some processing and send output to the browser. The scripts that don't work do some processing then send a "Location: " header to send to another page. The problem appears to be in the redirection, then. This is the error I get: "An I/O error occured during security authorization. Please try your connection again" Ok, then I've to check now POST+keepalive+redirection, too. What a nice thing that the HTTP protocol makes has such a lot of esoteric combinations possibleI'll investigate when I find time. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
