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
