RE: xml post
Status: Alpha
Brought to you by:
coroberti
Menu
▾
▴
RE: xml post
|
From: Matt L. <mat...@av...> - 2008-10-30 14:29:15
|
The decoded response is: Server: Apache/2.2.8 (Fedora)^M Allow: GET,HEAD,POST,OPTIONS,TRACE^M Content-Length: 320^M Connection: close^M Content-Type: text/html; charset=iso-8859-1^M ^M <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>405 Method Not Allowed</title> </head><body> <h1>Method Not Allowed</h1> <p>The requested method PUT is not allowed for the URL /nomadesk/index.phpTask.</p> <hr> <address>Apache/2.2.8 (Fedora) Server at 192.168.2.56 Port 80</address> </body></html> Ãà IH<8d>^@^@B^@^@^@B^@^@^@^@^L)ÃKÃ^@^L)¹^^Ã^H^@E^@^@4<82>ü@^@@^F1øè^BBG^&Ã^A^W^CxÃà IL<8d>^@^@B^@^@^@B^@^@^@^@^L)¹^^Ã^@^L)ÃKÃ^H^@E^@^@4uë@^@@^F? è^BGè^&ÃÃà IÃ<8d>^@^@B^@^@^@B^@^@^@^@^L)¹^^Ã^@^L)ÃKÃ^H^@E^@^@4uì@^@@^F?^Hè ^Cy^Oà ^BGè^B8<&ÃÃà IH<8e>^@^@B^@^@^@B^@^@^@^@^L)ÃKÃ^@^L)¹^^Ã^H^@E^@^@4<82>ý@^@@^F1÷ ^Cy^Oà è&Ã^A^W^Cy^@P<8c>j_&¦b^D«xä<80>^P^@>Â¥Â^@^@^A^A^H ^Oà The server wants a POST, but is there a way for me to pass a file in the CONF file to use as the POST stream? This is really easy to do with curl with the command: "curl -F file=@post.xml http://urltopostto.php", I figured it would be just as easy in curl-loader but so far, no luck! Thanks again for any help. Regards, Matt Love From: Robert Iakobashvili [mailto:cor...@gm...] Sent: Wednesday, October 29, 2008 1:30 PM To: curl-loader-devel Subject: Re: xml post Hi Matt, On Wed, Oct 29, 2008 at 1:26 PM, Matt Love <mat...@av...> wrote: REQUEST_TYPE=POST wireshark sees this: 761.972165 Vmware_d6:4b:dd -> Broadcast ARP Who has 192.168.2.56 <http://192.168.2.56/> ? Tell 192.168.2.71 <http://192.168.2.71/> 761.972667 Vmware_b9:1e:c2 -> Vmware_d6:4b:dd ARP 192.168.2.56 <http://192.168.2.56/> is at 00:0c:29:b9:1e:c2 761.972672 192.168.2.71 <http://192.168.2.71/> -> 192.168.2.56 <http://192.168.2.56/> TCP 47403 > http [SYN] Seq=0 Win=5840 Len=0 MSS=1460 TSV=167834233 TSER=0 WS=7 761.972832 192.168.2.56 <http://192.168.2.56/> -> 192.168.2.71 <http://192.168.2.71/> TCP http > 47403 [SYN, ACK] Seq=0 Ack=1 Win=5792 Len=0 MSS=1460 TSV=167910328 TSER=167834233 WS=7 761.972854 192.168.2.71 <http://192.168.2.71/> -> 192.168.2.56 <http://192.168.2.56/> TCP 47403 > http [ACK] Seq=1 Ack=1 Win=5888 Len=0 TSV=167834235 TSER=167910328 761.973090 192.168.2.71 <http://192.168.2.71/> -> 192.168.2.56 <http://192.168.2.56/> TCP [TCP segment of a reassembled PDU] 761.973265 192.168.2.56 <http://192.168.2.56/> -> 192.168.2.71 <http://192.168.2.71/> TCP http > 47403 [ACK] Seq=1 Ack=212 Win=6912 Len=0 TSV=167910329 TSER=167834235 761.973660 192.168.2.56 <http://192.168.2.56/> -> 192.168.2.71 <http://192.168.2.71/> HTTP HTTP/1.1 100 Continue 761.973665 192.168.2.71 <http://192.168.2.71/> -> 192.168.2.56 <http://192.168.2.56/> TCP 47403 > http [ACK] Seq=212 Ack=26 Win=5888 Len=0 TSV=167834236 TSER=167910329 761.973907 192.168.2.71 <http://192.168.2.71/> -> 192.168.2.56 <http://192.168.2.56/> HTTP PUT /nomadesk/index.phpTask?Navigator::Task=ReceiveMessage HTTP/1.1 761.974298 192.168.2.56 <http://192.168.2.56/> -> 192.168.2.71 <http://192.168.2.71/> HTTP HTTP/1.1 405 Method Not Allowed (text/html) 761.974431 192.168.2.56 <http://192.168.2.56/> -> 192.168.2.71 <http://192.168.2.71/> TCP http > 47403 [FIN, ACK] Seq=570 Ack=595 Win=7936 Len=0 TSV=167910330 TSER=167834236 761.974435 192.168.2.71 <http://192.168.2.71/> -> 192.168.2.56 <http://192.168.2.56/> TCP 47403 > http [ACK] Seq=595 Ack=571 Win=7040 Len=0 TSV=167834237 TSER=167910330 761.974609 192.168.2.71 <http://192.168.2.71/> -> 192.168.2.56 <http://192.168.2.56/> TCP 47403 > http [FIN, ACK] Seq=595 Ack=571 Win=7040 Len=0 TSV=167834237 TSER=167910330 761.974734 192.168.2.56 <http://192.168.2.56/> -> 192.168.2.71 <http://192.168.2.71/> TCP http > 47403 [ACK] Seq=571 Ack=596 Win=7936 Len=0 TSV=167910330 TSER=167834237 In the sourceforge TODO doc for curl-loader I see that "transparent support for POST-ing some file, e.g. a SOAP file" is on the TODO list for the next beta. This seems to be exactly what I need. So would there be a non-transparent way (workaround) to achieve this same thing in the current release? What we see from the wireshark trace is that the first HTTP is most probably POST or PUT (you may wish to use the "Decode AS" function of wireshark GUI or look at the capture text strings) with subsequent 100 Continue and further PUT HTTP request attempt, responded by 405 + more decoded Could you, please, either attach the capture or send the HTTP-decoded stream? Thanks. Robert |
