httpost: empty line between headers

This topic has 9 replies, 5 voices, and was last updated 15 years, 1 month ago by Charlie Bursell.

Creator

Topic
June 16, 2009 at 8:44 am #50973
Serena Nichetti
Participant
Dear all,

I need to send the following HTTP request:

POST /dataexchange.asmx HTTP/1.1

Host: 127.0.0.1

Content-Type: text/xml; charset=utf-8

Content-Length: 290

SOAPAction: “http://tempuri.org/GetWSVersion“

http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:soap=”http://schemas.xmlsoap.org/soap/envelope/“>

http://tempuri.org/” />

I’m using the httppost command with {DEBUG 1} and I see that between the headers there are empty lines.

They are not accepted by the Web Server. It stops to read the headers at first empty line.

I’m running qdx5.6

tcl>httppost {{URL http://127.0.0.1/DataExchange.asmx} {METHOD POST} {HEADERS {{Content-Type “text/xml; charset=utf-8”} {Content-Length 290} {SOAPAction “http://tempuri.org/GetWSVersion“}}} {DATA {http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:soap=”http://schemas.xmlsoap.org/soap/envelope/”> xmlns=”http://tempuri.org/” />}} {DEBUG 1}}

* About to connect() to 127.0.0.1 port 80 (#0)

* Trying 127.0.0.1… * connected

* Connected to 127.0.0.1 (127.0.0.1) port 80 (#0)

> POST /DataExchange.asmx HTTP/1.1

User-Agent: Quovadx CISAgent

Host: 127.0.0.1

Accept: */*

Content-Length: 290

SOAPAction: http://tempuri.org/GetWSVersion

From: anonymous@unknown.com

Connection: close

Content-Type: text/xml; charset=utf-8

Does it exist a way to send HTTP headers without empty line?

POST /DataExchange.asmx HTTP/1.1

User-Agent: Quovadx CISAgent

Host: 127.0.0.1

Accept: */*

Content-Length: 290

SOAPAction: http://tempuri.org/GetWSVersion

From: anonymous@unknown.com

Connection: close

Content-Type: text/xml; charset=utf-8

Thanks

Serena
Creator

Topic

Viewing 8 reply threads

Author

Replies
- June 16, 2009 at 1:19 pm #68244
  Charlie Bursell
  Participant
  There is a problem with httppost and headers especially if there are linefeeds.
  
  I would recommend using tclCurl instead which I beleive is supplied with 5.6
  
  If you don’t mind being a bit of a Guinea Pig, I have rewritten the httpQuery procedure to use TclCurl. I have tested it but it probably needs a lot more.
  
  I have enclosed it if you want to give it a try. If you do try it and have problems, contact ne via e-mail: cbursell@healthvision.com
- September 25, 2009 at 7:52 pm #68245
  Lawrence Williams
  Participant
  I downloaded and attempted to use this cURL based replacement tcl proc, but haven’t had any luck. I assumed it was a ‘drop-in’ replacement for the original httpQuery, but it appears that is not the case.
  
  Anyone that could give me some assistance with replacing the original httpQuery (non-cURL) with the TclCurl version would be most appreciated.
  
  When it runs from the Http client protocol Query TPS, I get a thread panic and the process shuts down. The error in the process log is “unrecognized command”. Is there something I need to add to the tcl proc to ‘pull-in’ the TclCurl package ?
- September 25, 2009 at 7:56 pm #68246
  Charlie Bursell
  Participant
  Send me an e-mail with the errors you are getting and I’ll try to help. I will get to it when I can.
  
  It should work just as the original except better 😀
  
  charlie.bursell@helathvision.com
- September 25, 2009 at 9:31 pm #68247
  Lawrence Williams
  Participant
  I just emailed the logfile…. note: your email address in the previous post had healthvision spelled wrong 🙂
- September 28, 2009 at 2:47 pm #68248
  Bob Richardson
  Participant
  Greetings,
  
  [AIX5.3 TL8 SP7 shop]
  
  We are using the CIS5.6R2 TclCurl for doing https posts of 271 X12 to a payer website. We have configured a Protocol:http-client thread that specifies our own home-grown driver (TCL) that acquires the TclCurl package. We have chosen to pass the username and password as arguments to this driver.
  
  See the attachments of a screen shot for the protocol and TCL driver for your review. This works fine so far and we plan to evaluate it for the upcoming 5.8 version.
  
  You can play with the driver in a tcl shell with a few modifications.
  
  I hope this will prove useful to you.
- October 8, 2009 at 3:54 pm #68249
  Lawrence Williams
  Participant
  Thank you for the help Robert.
  
  I was able to get it working with the original httppost (without cURL), by having the programmer include some html code in the pl/sql script…therefore when the httppost command executes it is finding an actual html page.
  
  I am now working on getting the httpQueryCurl that Charlie posted working… I just need to figure out how to grab the response for the reply….. for instance the httpQueryCurl is grabbing the CURLBODY for the reply but I need the actual response (i.e. HTTP/1.1 200 OK). I can see the response when I turn on the debug option in the httpQueryCurl.tcl, but I’m just not sure ‘yet’ how to pull that in for the reply function.
- October 8, 2009 at 4:04 pm #68250
  Charlie Bursell
  Participant
  Send me an e-mail with the particulars Lawrence and I will take a look at it as soon as I can. I am still trying to catch up after the User’s Conference 🙂
  
  I do appreciate you helping me to test this.
  
  charlie.bursell@healthvision.com
- October 29, 2009 at 5:54 pm #68251
  James Nelson
  Participant
  We’re having the same issue with the blank line between headers. When I tried to use the httpQueryCurl proc, it bombed complaining that ‘curlSubs::PKGERR’ is an unknown variable. I’m still working on correcting that error, but if someone’s already done that it doesn’t make sense for me to reinvent the wheel. 🙂
- October 29, 2009 at 6:05 pm #68252
  Charlie Bursell
  Participant
  I think there was a typo in the original that I uploaded. Try this one
Author

Replies

Viewing 8 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.