Re: [U2] Viewing HTTP headers when using UniData submitRequest()
>From this the http headers are POST /badcock/services/DecisionService HTTP/1.0 Date: Thu, 22 Apr 2010 12:59:12 GMT User-Agent: UniData 7.2.x Authorization: Basic aW50ZXJjb25uZWN0LnVhdDp3ZXRjMg== Content-Type: application/x-www-form-urlencoded Content-Length: 1782 The payload is the xml after that, And the response is a 404. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Graham, Dave Sent: 22 April 2010 17:41 To: U2 Users List Subject: Re: [U2] Viewing HTTP headers when using UniData submitRequest() OK - Just remember, you asked for it 04/22/2010 09:11:44 [ 3809296 2973944 ] addRequestParameter ... host=interconnect.ct.sts.equifax.com,parm=service_name:,type=x-www-form-urlencoded 04/22/2010 09:11:44 [ 3809296 2973944 ] addRequestParameter: added service_name=, type x-www-form-urlencoded 04/22/2010 09:11:54 [ 3809296 2973944 ] submitRequest ... Var 10276198: host=interconnect.ct.sts.equifax.com,timeout=1 04/22/2010 09:11:54 [ 3809296 2973944 ] new header User-Agent added with value UniData 7.2.x 04/22/2010 09:11:54 [ 3809296 2973944 ] Assembled Request: POST /badcock/services/DecisionService HTTP/1.0 Date: Thu, 22 Apr 2010 12:59:12 GMT User-Agent: UniData 7.2.x Authorization: Basic aW50ZXJjb25uZWN0LnVhdDp3ZXRjMg== Content-Type: application/x-www-form-urlencoded Content-Length: 1782 http://xml.equifax.com/XMLSchema/InterConnect"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://xml.equifax.com/XMLSchema/InterConnect..\xsd\InterConnectRequestImpl1-0.xsd";> 1.0 1014 testing-INT-627529463 2010-22-04T08:58:54.0-5:00 999HF00231 BCF marian briesch -- 627529463 Addresses 225 may av. macon GA 31204 ChannelID S StoreID 04/22/2010 09:11:54 [ 3809296 2973944 ] HTTP_START: timeout=1 04/22/2010 09:11:54 [ 3809296 2973944 ] HTTP_CONNECT 04/22/2010 09:11:54 [ 3809296 2973944 ] new host 10274f70:interconnect.ct.sts.equifax.com:443 allocated (proxy:no) 04/22/2010 09:11:54 [ 3809296 2973944 ] host interconnect.ct.sts.equifax.com:443 not found in hostList 04/22/2010 09:11:54 [ 3809296 2973944 ] socket 10274ff0 allocated 04/22/2010 09:11:54 [ 3809296 2973944 ] start SSLbinding ... 04/22/2010 09:11:54 [ 3809296 2973944 ] loading SSL method ... 04/22/2010 09:11:54 [ 3809296 2973944 ] Info: No self-cert file set in context (OK for client)! 04/22/2010 09:11:54 [ 3809296 2973944 ] Info: No private key availble, OK for client. 04/22/2010 09:11:54 [ 3809296 2973944 ] loading random seed data from /devel/ud/develar/.rnd 04/22/2010 09:11:54 [ 3809296 2973944 ] begin SSL connect ... 04/22/2010 09:11:54 [ 3809296 2973944 ] SSL trace: Handshake: start 04/22/2010 09:11:54 [ 3809296 2973944 ] SSL trace: Loop: before/connect initialization ===>BIO_write[3809296 3809296]: write len=126 80 7C 01 03 00 00 63 00 00 00 10 00 00 39 00 00 38 00 00 35 00 00 16 00 00 13 00 00 0A 07 00 C0 00 00 33 00 00 32 00 00 2F 03 00 80 00 00 66 00 00 05 00 00 04 01 00 80 08 00 80 00 00 63 00 00 62 00 00 61 00 00 15 00 00 12 00 00 09 06 00 40 00 00 65 00 00 64 00 00 60 00 00 14 00 00 11 00 00 08 00 00 06 04 00 80 00 00 03 02 00 80 02 10 B3 C5 38 77 4E 35 30 67 CA 6E 0B C0 7D 6C 04/22/2010 09:11:54 [ 3809296 2973944 ] SSL trace: Loop: SSLv2/v3 write client hello A ===>BIO_read[3809296 3809296]: read len=7 16 03 00 06 F9 02 00 04/22/2010 09:11:55 [ 3809296 2973944 ] ssl3_read_bytes: calling ssl3_get_record() 04/22/2010 09:11:55 [ 3809296 2973944 ] ssl3_get_record: calling ssl3_read_n asking 5 bytes data 04/22/2010 09:11:55 [ 3809296 2973944 ] ssl3_read_n: return 5 bytes from buf[0] 04/22/2010 09:11:55 [ 3809296 2973944 ] ssl3_get_record: ssl3_read_n returned with 5 04/22/2010 09:11:55 [ 3809296 2973944 ] ssl3_get_record: 2-calling ssl3_read_n asking 1785 bytes data 04/22/2010 09:11:55 [ 3809296 2973944 ] ssl3_read_n: calling BIO_read() asking 1783 bytes to buf[7] ===>BIO_read[3809296 3809296]: read len=1783 00 46 03 00 00 00 6C BE 20 1A 51 AD 14 B4 CD 9E 04 D3 DC 99 79 FA A3 DD 2F 19 A7 37 D1 12 32 96 E3 2B 0C C2 20 08 82 2E A6 FD 25 B4 27 05 46 60 80 B5 54 38 11 24 50 05 9A FB 47 AD 0C CA B8 DF 3B 9C 5C 71 33 00 04 00 0B 00 06 A7 00 06 A4 00 03 73 30 82 03 6F 30 82 02 D8 A0 03 02 01 02 02 10 72 92 0C A0 00 67 95 36 D7 A3 27 71 F6 5D 39 78 30 0D 06 09 2A 86 48 86 F7 0D 01 01 05 05 00 30 81 CE 31 0B 30 09 06 03 55 04 06 13 02 5A 41 31 15 30 13 06 03 55 04 08 13 0C 57 65 73 74 65 72 6E 20 43 61 70 65 31 12 30 10 06 03 55 04 07 13 09 43 61 70 65 20 54 6F 77 6E 31 1D 30 1B 06 03 55 04 0A 13 14 54 68 61 77 74 65 20 43 6F 6E 73 75 6C 74 69 6E 67 20 63 63 3
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
404? Doesn't look like a header thing, looks like the URL is wrong. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
Socket 10274ff0: 452 chars read 04/22/2010 09:11:55 [ 3809296 2973944 ] HTTP_CHKSTAT 04/22/2010 09:11:55 [ 3809296 2973944 ] Response: Status line: HTTP/1.1 404 Not found 04/22/2010 09:11:55 [ 3809296 2973944 ] SubmitRequest: server HTTP version 1.1 04/22/2010 09:11:55 [ 3809296 2973944 ] SubmitRequest: response status 404: Not found 04/22/2010 09:11:55 [ 3809296 2973944 ] Response message headers: Server: Sun-ONE-Web-Server/6.1 Date: Thu, 22 Apr 2010 13:14:19 GMT Content-length: 292 Content-type: text/html Connection: close 04/22/2010 09:11:55 [ 3809296 2973944 ] Response message body(may be partial) length: 292 04/22/2010 09:11:55 [ 3809296 2973944 ] Response message body: Not Found Not Found The requested object does not exist on this server. The link you followed is either outdated, inaccurate, or the server has been instructed not to let you have it. 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = Server: 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = Sun-ONE-Web-Server/6.1 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = Date: 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = Thu, 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = 22 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = Apr 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = 2010 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = 13:14:19 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = GMT 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = Content-length: 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = 292 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = Content-type: 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = text/html 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = Connection: 04/22/2010 09:11:55 [ 3809296 2973944 ] next field = close 04/22/2010 09:11:55 [ 3809296 2973944 ] HTTP_ERROR, status=0 04/22/2010 09:11:55 [ 3809296 2973944 ] found session(key:interconnect.ct.sts.equifax.com443U2tempctx,1028d530) in cache 04/22/2010 09:11:55 [ 3809296 2973944 ] interconnect.ct.sts.equifax.com443U2tempctx: session(CIIupv0ltCcFRmCAtVQ4ESRQBZr7R60MyrjfO5xccTM=,1028d530) refreshed in cache,new count=2 04/22/2010 09:11:55 [ 3809296 2973944 ] Socket 10274ff0 closed: 0(No error) 0(No error) 04/22/2010 09:11:55 [ 3809296 2973944 ] socket 10274ff0 freed 04/22/2010 09:11:55 [ 3809296 2973944 ] Host 10274f70 freed -F -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King Sent: Thursday, April 22, 2010 11:27 AM To: U2 Users List Subject: Re: [U2] Viewing HTTP headers when using UniData submitRequest() Could you post the output of your protocol log? Maybe someone here might see something? ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
Agreed. I wouldn't want to sift through the escaped post string with my eyes. It wouldn't be difficult to write something that unescapes the control characters though. I've got log4J running in our web application and I log all the stuff I need on that end. The protocolLogging feature is still useful for debugging issues when the request is not making to the webserver at all or, as in Kevin's case, when you're posting to an external server and don't have access to logs on that end. If you're on a Unix system the open source packet sniffer tcpflow does a real nice job of formatting the HTML and headers in a human readable format by default. It's much simpler than working with tcpdump if you only want to see the HTML body and headers. http://www.owlriver.com/tips/tcpflow-tutorial/ -Ben On Thu, 2010-04-22 at 11:24 -0400, Graham, Dave wrote: > I've tried that. However even at level 10 logging I don't get a concise > view of what the receiving web server 'sees' in a format that I can go > to my vendor and say "look at this, isn't that what your documentation > says?" > > I've used protocolLogging forever in diagnosing socket issues and it was > my first try - however not being a real HTTP guru, having a recalcitrant > vendor and using SSL is more than a tiny bit to chew off at one time. > > Our web guys have put together a site I can go to with my data and it > emails me a dump of all of the variables available to IIS, in an IIS > (sort of) format so here's hoping that will give me some ammunition to > deal with the vendor. > > Sure would be nice to have a tool within the UniData environment that > would return what is about to be sent out of the HTTP(s) port though - > that 'raw' text would go a long way to settling disputes like this one. > > -F > > -Original Message- > From: u2-users-boun...@listserver.u2ug.org > [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Ben Souther > Sent: Thursday, April 22, 2010 11:15 AM > To: U2 Users List > Subject: Re: [U2] Viewing HTTP headers when using UniData > submitRequest() > > Look at the docs for protocolLogging > > > > 0155 ** > > 0156 IF DO.LOGGING THEN > > 0157 res=protocolLogging(LOGFILE,"ON",10) > > 0158 END > > 0159 ** > > > It's pretty comprehensive. > Here is the output from one of my calls: > > > 04/22/2010 11:11:44 [ 760 192 ] createRequest ... 114b68 for Var > 106df0: > URL=http://192.168.0.59:8080/hrp53/MailService/SendEmail,method=POST:app > lication/x-www-form-urlencoded > 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader: standard header > Content-Type=application/x-www-form-urlencoded > 04/22/2010 11:11:44 [ 760 192 ] new header Content-Type added with > value application/x-www-form-urlencoded > 04/22/2010 11:11:44 [ 760 192 ] current Request date: Thu, 22 Apr 2010 > 15:11:44 GMT > 04/22/2010 11:11:44 [ 760 192 ] Var entry 106df0 inserted in varlist > 89ef0 > > 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader ... > host=192.168.0.59:8080,header=User-Agent:HRP SendEmail > 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader: standard header > User-Agent=HRP SendEmail > 04/22/2010 11:11:44 [ 760 192 ] new header User-Agent added with value > HRP SendEmail > > 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader ... > host=192.168.0.59:8080,header=Content-Type:application/x-www-form-urlenc > oded > 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader: standard header > Content-Type=application/x-www-form-urlencoded > 04/22/2010 11:11:44 [ 760 192 ] header Content-Type valued changed > from to application/x-www-form-urlencoded > > 04/22/2010 11:11:44 [ 760 192 ] submitRequest ... Var 106df0: > host=192.168.0.59:8080,timeout=12000 > 04/22/2010 11:11:44 [ 760 192 ] new header User-Agent added with value > UniData 7.2.x > 04/22/2010 11:11:44 [ 760 192 ] Assembled Request: > POST /hrp53/MailService/SendEmail HTTP/1.0 > Date: Thu, 22 Apr 2010 15:11:44 GMT > User-Agent: HRP SendEmail > Content-Type: application/x-www-form-urlencoded > Content-Length: 615 > > recipients=bsouther%40fwdco%2Ecom%2Cben%40souther%2Eus&from=admin% > 40fwdco%2Ecom&subject=Test+Email+from%3A+bsouther&body=This+is++a+test > +from%3A+bsouther%0AThis+is+a+%0Abroken+line%2E%0AFrom+reed&host=smtp% > 2Espamarrest%2Ecom&port=25&smtp_user=bsouther%2Efwdco%2Ecom&html_body=% > 3Chtml%3E+%3Chead%3E+++%3Ctitle%3Etest+message%3C%2Ftitle%3E+%3C%2Fhead% > 3E+%3Cbody%3E++%3Cp%3EThis+is+the+HTML+version+of+the+message%3C%2Fp%3E > ++%3Cb
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
Well, IIS can do HTTP just like Apache. (Well, not exactly, but you know what I mean.) But I like the protocolLogging option mentioned above. You might try that first. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
Could you post the output of your protocol log? Maybe someone here might see something? ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
I've tried that. However even at level 10 logging I don't get a concise view of what the receiving web server 'sees' in a format that I can go to my vendor and say "look at this, isn't that what your documentation says?" I've used protocolLogging forever in diagnosing socket issues and it was my first try - however not being a real HTTP guru, having a recalcitrant vendor and using SSL is more than a tiny bit to chew off at one time. Our web guys have put together a site I can go to with my data and it emails me a dump of all of the variables available to IIS, in an IIS (sort of) format so here's hoping that will give me some ammunition to deal with the vendor. Sure would be nice to have a tool within the UniData environment that would return what is about to be sent out of the HTTP(s) port though - that 'raw' text would go a long way to settling disputes like this one. -F -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Ben Souther Sent: Thursday, April 22, 2010 11:15 AM To: U2 Users List Subject: Re: [U2] Viewing HTTP headers when using UniData submitRequest() Look at the docs for protocolLogging 0155 ** 0156 IF DO.LOGGING THEN 0157 res=protocolLogging(LOGFILE,"ON",10) 0158 END 0159 ** It's pretty comprehensive. Here is the output from one of my calls: 04/22/2010 11:11:44 [ 760 192 ] createRequest ... 114b68 for Var 106df0: URL=http://192.168.0.59:8080/hrp53/MailService/SendEmail,method=POST:app lication/x-www-form-urlencoded 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader: standard header Content-Type=application/x-www-form-urlencoded 04/22/2010 11:11:44 [ 760 192 ] new header Content-Type added with value application/x-www-form-urlencoded 04/22/2010 11:11:44 [ 760 192 ] current Request date: Thu, 22 Apr 2010 15:11:44 GMT 04/22/2010 11:11:44 [ 760 192 ] Var entry 106df0 inserted in varlist 89ef0 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader ... host=192.168.0.59:8080,header=User-Agent:HRP SendEmail 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader: standard header User-Agent=HRP SendEmail 04/22/2010 11:11:44 [ 760 192 ] new header User-Agent added with value HRP SendEmail 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader ... host=192.168.0.59:8080,header=Content-Type:application/x-www-form-urlenc oded 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader: standard header Content-Type=application/x-www-form-urlencoded 04/22/2010 11:11:44 [ 760 192 ] header Content-Type valued changed from to application/x-www-form-urlencoded 04/22/2010 11:11:44 [ 760 192 ] submitRequest ... Var 106df0: host=192.168.0.59:8080,timeout=12000 04/22/2010 11:11:44 [ 760 192 ] new header User-Agent added with value UniData 7.2.x 04/22/2010 11:11:44 [ 760 192 ] Assembled Request: POST /hrp53/MailService/SendEmail HTTP/1.0 Date: Thu, 22 Apr 2010 15:11:44 GMT User-Agent: HRP SendEmail Content-Type: application/x-www-form-urlencoded Content-Length: 615 recipients=bsouther%40fwdco%2Ecom%2Cben%40souther%2Eus&from=admin% 40fwdco%2Ecom&subject=Test+Email+from%3A+bsouther&body=This+is++a+test +from%3A+bsouther%0AThis+is+a+%0Abroken+line%2E%0AFrom+reed&host=smtp% 2Espamarrest%2Ecom&port=25&smtp_user=bsouther%2Efwdco%2Ecom&html_body=% 3Chtml%3E+%3Chead%3E+++%3Ctitle%3Etest+message%3C%2Ftitle%3E+%3C%2Fhead% 3E+%3Cbody%3E++%3Cp%3EThis+is+the+HTML+version+of+the+message%3C%2Fp%3E ++%3Cbr+%2F%3E+Isn%27t+this+%3Cb%3Enifty%3C%2Fb%3E%3F%3Cbr+%2F%3E++% 3Cimg+src%3D%27http%3A%2F%2Fwww%2Efwdco%2Ecom%2Ftemplates%2F1%2Fimages% 2Ftop%5Flogo%2Egif%27++%2F%3E+%3C%2Fbody%3E%3C%2Fhtml%3E 04/22/2010 11:11:44 [ 760 192 ] HTTP_START: timeout=12000 04/22/2010 11:11:44 [ 760 192 ] HTTP_CONNECT 04/22/2010 11:11:44 [ 760 192 ] new host b1508:192.168.0.59:8080 allocated (proxy:no) 04/22/2010 11:11:44 [ 760 192 ] host 192.168.0.59:8080 not found in hostList 04/22/2010 11:11:49 [ 760 192 ] socket 10c658 allocated 04/22/2010 11:11:49 [ 760 192 ] Non-secure Socket 10c658(192.168.0.59:8080) opened 04/22/2010 11:11:49 [ 760 192 ] HTTP_SEND 04/22/2010 11:11:49 [ 760 192 ] Socket 10c658: 795 chars sent 04/22/2010 11:11:49 [ 760 192 ] HTTP_GETSTAT 04/22/2010 11:11:49 [ 760 192 ] Socket 10c658: 219 chars read 04/22/2010 11:11:49 [ 760 192 ] HTTP_CHKSTAT 04/22/2010 11:11:49 [ 760 192 ] Response: Status line: HTTP/1.1 200 OK 04/22/2010 11:11:49 [ 760 192 ] SubmitRequest: server HTTP version 1.1 04/22/2010 11:11:49 [ 760 192 ] SubmitRequest: response status 200: OK 04/22/2010 11:11:49 [ 760 192 ] Response message headers: Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=D70D81C7ED0445A9750B04AFDB06DE87; Path=/hrp53 Content-Length: 27 Date: Thu, 22 Apr 2010 15:10:52 GMT Connection: close 04/22/2010 11:11:49 [ 760 192 ] Respon
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
Regrettably we have no knowledge of Apache here so it IIS or nothing and to top it off the 1 guy in the office that is most familiar with doing any of this kind of stuff is out -F -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King Sent: Thursday, April 22, 2010 11:10 AM To: U2 Users List Subject: Re: [U2] Viewing HTTP headers when using UniData submitRequest() Whether HTTP or HTTPS, the headers should be the same, right? So why not test with a simple HTTP connection instead of going through the creative dentistry of setting up IIS w/ HTTPS? ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
Try something like fiddler2, or some other packet sniffer. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Graham, Dave Sent: Thursday, April 22, 2010 8:06 AM To: U2 Users List Subject: Re: [U2] Viewing HTTP headers when using UniData submitRequest() I've been working with 2 of our 'web heads' for the past several hours trying to do just that - apparently, since its an HHTPS request and that we're an IIS shop, it's not as simple as I thought - one of the guys is cursing me already! The problem with the header is that we don't know what the problem is - the vendor isn't being very forthcoming - they have security concerns - and I'm looking at the protoclLogging logs and it looks OK to me. But we are talking apples V oranges here and until I can go back to the vendor and say "I'm passing you this value as this element of this header" I'm sort of fumbling around in the dark. -F -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King Sent: Thursday, April 22, 2010 10:59 AM To: U2 Users List Subject: Re: [U2] Viewing HTTP headers when using UniData submitRequest() Not sure how to do it strictly in Unidata, but you might setup a simple Apache server that echos the headers back in the contents and then use this to test the Unidata headers. Incidentally, what header seems to be the problem? -K ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
Good info, Ben! Thanks for sharing! ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
Look at the docs for protocolLogging 0155 ** 0156 IF DO.LOGGING THEN 0157 res=protocolLogging(LOGFILE,"ON",10) 0158 END 0159 ** It's pretty comprehensive. Here is the output from one of my calls: 04/22/2010 11:11:44 [ 760 192 ] createRequest ... 114b68 for Var 106df0: URL=http://192.168.0.59:8080/hrp53/MailService/SendEmail,method=POST:application/x-www-form-urlencoded 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader: standard header Content-Type=application/x-www-form-urlencoded 04/22/2010 11:11:44 [ 760 192 ] new header Content-Type added with value application/x-www-form-urlencoded 04/22/2010 11:11:44 [ 760 192 ] current Request date: Thu, 22 Apr 2010 15:11:44 GMT 04/22/2010 11:11:44 [ 760 192 ] Var entry 106df0 inserted in varlist 89ef0 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader ... host=192.168.0.59:8080,header=User-Agent:HRP SendEmail 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader: standard header User-Agent=HRP SendEmail 04/22/2010 11:11:44 [ 760 192 ] new header User-Agent added with value HRP SendEmail 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader ... host=192.168.0.59:8080,header=Content-Type:application/x-www-form-urlencoded 04/22/2010 11:11:44 [ 760 192 ] setRequestHeader: standard header Content-Type=application/x-www-form-urlencoded 04/22/2010 11:11:44 [ 760 192 ] header Content-Type valued changed from to application/x-www-form-urlencoded 04/22/2010 11:11:44 [ 760 192 ] submitRequest ... Var 106df0: host=192.168.0.59:8080,timeout=12000 04/22/2010 11:11:44 [ 760 192 ] new header User-Agent added with value UniData 7.2.x 04/22/2010 11:11:44 [ 760 192 ] Assembled Request: POST /hrp53/MailService/SendEmail HTTP/1.0 Date: Thu, 22 Apr 2010 15:11:44 GMT User-Agent: HRP SendEmail Content-Type: application/x-www-form-urlencoded Content-Length: 615 recipients=bsouther%40fwdco%2Ecom%2Cben%40souther%2Eus&from=admin% 40fwdco%2Ecom&subject=Test+Email+from%3A+bsouther&body=This+is++a+test +from%3A+bsouther%0AThis+is+a+%0Abroken+line%2E%0AFrom+reed&host=smtp% 2Espamarrest%2Ecom&port=25&smtp_user=bsouther%2Efwdco%2Ecom&html_body=% 3Chtml%3E+%3Chead%3E+++%3Ctitle%3Etest+message%3C%2Ftitle%3E+%3C%2Fhead% 3E+%3Cbody%3E++%3Cp%3EThis+is+the+HTML+version+of+the+message%3C%2Fp%3E ++%3Cbr+%2F%3E+Isn%27t+this+%3Cb%3Enifty%3C%2Fb%3E%3F%3Cbr+%2F%3E++% 3Cimg+src%3D%27http%3A%2F%2Fwww%2Efwdco%2Ecom%2Ftemplates%2F1%2Fimages% 2Ftop%5Flogo%2Egif%27++%2F%3E+%3C%2Fbody%3E%3C%2Fhtml%3E 04/22/2010 11:11:44 [ 760 192 ] HTTP_START: timeout=12000 04/22/2010 11:11:44 [ 760 192 ] HTTP_CONNECT 04/22/2010 11:11:44 [ 760 192 ] new host b1508:192.168.0.59:8080 allocated (proxy:no) 04/22/2010 11:11:44 [ 760 192 ] host 192.168.0.59:8080 not found in hostList 04/22/2010 11:11:49 [ 760 192 ] socket 10c658 allocated 04/22/2010 11:11:49 [ 760 192 ] Non-secure Socket 10c658(192.168.0.59:8080) opened 04/22/2010 11:11:49 [ 760 192 ] HTTP_SEND 04/22/2010 11:11:49 [ 760 192 ] Socket 10c658: 795 chars sent 04/22/2010 11:11:49 [ 760 192 ] HTTP_GETSTAT 04/22/2010 11:11:49 [ 760 192 ] Socket 10c658: 219 chars read 04/22/2010 11:11:49 [ 760 192 ] HTTP_CHKSTAT 04/22/2010 11:11:49 [ 760 192 ] Response: Status line: HTTP/1.1 200 OK 04/22/2010 11:11:49 [ 760 192 ] SubmitRequest: server HTTP version 1.1 04/22/2010 11:11:49 [ 760 192 ] SubmitRequest: response status 200: OK 04/22/2010 11:11:49 [ 760 192 ] Response message headers: Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=D70D81C7ED0445A9750B04AFDB06DE87; Path=/hrp53 Content-Length: 27 Date: Thu, 22 Apr 2010 15:10:52 GMT Connection: close 04/22/2010 11:11:49 [ 760 192 ] Response message body(may be partial) length: 27 04/22/2010 11:11:49 [ 760 192 ] Response message body: error_code=0&error_message= 04/22/2010 11:11:49 [ 760 192 ] next field = Server: 04/22/2010 11:11:49 [ 760 192 ] next field = Apache-Coyote/1.1 04/22/2010 11:11:49 [ 760 192 ] next field = Set-Cookie: 04/22/2010 11:11:49 [ 760 192 ] next field = JSESSIONID=D70D81C7ED0445A9750B04AFDB06DE87; 04/22/2010 11:11:49 [ 760 192 ] next field = Path=/hrp53 04/22/2010 11:11:49 [ 760 192 ] next field = Content-Length: 04/22/2010 11:11:49 [ 760 192 ] next field = 27 04/22/2010 11:11:49 [ 760 192 ] next field = Date: 04/22/2010 11:11:49 [ 760 192 ] next field = Thu, 04/22/2010 11:11:49 [ 760 192 ] next field = 22 04/22/2010 11:11:49 [ 760 192 ] next field = Apr 04/22/2010 11:11:49 [ 760 192 ] next field = 2010 04/22/2010 11:11:49 [ 760 192 ] next field = 15:10:52 04/22/2010 11:11:49 [ 760 192 ] next field = GMT 04/22/2010 11:11:49 [ 760 192 ] next field = Connection: 04/22/2010 11:11:49 [ 760 192 ] next field = close 04/22/2
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
Whether HTTP or HTTPS, the headers should be the same, right? So why not test with a simple HTTP connection instead of going through the creative dentistry of setting up IIS w/ HTTPS? ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
I've been working with 2 of our 'web heads' for the past several hours trying to do just that - apparently, since its an HHTPS request and that we're an IIS shop, it's not as simple as I thought - one of the guys is cursing me already! The problem with the header is that we don't know what the problem is - the vendor isn't being very forthcoming - they have security concerns - and I'm looking at the protoclLogging logs and it looks OK to me. But we are talking apples V oranges here and until I can go back to the vendor and say "I'm passing you this value as this element of this header" I'm sort of fumbling around in the dark. -F -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King Sent: Thursday, April 22, 2010 10:59 AM To: U2 Users List Subject: Re: [U2] Viewing HTTP headers when using UniData submitRequest() Not sure how to do it strictly in Unidata, but you might setup a simple Apache server that echos the headers back in the contents and then use this to test the Unidata headers. Incidentally, what header seems to be the problem? -K ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Viewing HTTP headers when using UniData submitRequest()
Not sure how to do it strictly in Unidata, but you might setup a simple Apache server that echos the headers back in the contents and then use this to test the Unidata headers. Incidentally, what header seems to be the problem? -K ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
