| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| HTTP Header Issue - v6.0 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Paul D |
 Posted: Mon Aug 13, 2007 6:10 am Post subject: HTTP Header Issue - v6.0 |
 |
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
We've run into an interesting issue calling a vendor package with an HTTP request. It's got a basic XML payload. We are running 6.0 on AIX and using the HTTP request node in the middle of our flow. We are letting the HTTP headers generate. Our request goes out fine, but it appears that the HTTP response header has issues.
| Quote: |
RecoverableException BIP3156S: An error was found whilst parsing 'HTTP' header data. A 'HTTP' header name is empty or contains invalid characters at position: 203.
A 'HTTP' header name cannot be empty or contain invalid characters. |
The vendor app processes the request fine and sends the response back to us so we are confident it's in the reply header. A trace node is not showing us the header so we don't have good visability into what's in there. Is there anything that we can use (shareware utility?) that would work well for this. User trace and service trace are not helping either.
_________________
Thanks!!!
Paul D |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Aug 13, 2007 11:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Depends on where you can test this from.
If you can call this HTTPRequest from a developer workstation, the Toolkit comes with a TCP/IP Monitor built in (it's a view).
If you can't call it from a developer workstation, you can set up NetTool (open source project from sourceforge) to monitor.
In either case, you will end up using the monitor as a proxy - change the HTTPRequest node to talk to the local port, and have the local port forwarded to the actual end point.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mgk |
| Posted: Mon Aug 13, 2007 11:13 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
And, when you see what the app is sending back to the request node on the wire, please post it here...
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| Paul D |
| Posted: Mon Aug 13, 2007 6:10 pm Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
Here is some output from a service trace we were able to get..
| Code: |
2007-08-13 10:20:50.928775 12366 >> } ImbHTTPHeaderParser::extractReasonPhrase , 15, 'OK'
2007-08-13 10:20:50.928783 12366 >> } ImbHTTPHeaderParser::extractHTTPResponseData , true
2007-08-13 10:20:50.928791 12366 >> } ImbHTTPHeaderParser::parseHttpHeaderLine , 17
2007-08-13 10:20:50.928798 12366 >> { ImbRFC822HeaderParser::parseHeaders
2007-08-13 10:20:50.928802 12366 >> { ImbRFC822HeaderParser::checkForEndOfHeaders , 17
2007-08-13 10:20:50.928810 12366 >> } ImbRFC822HeaderParser::checkForEndOfHeaders , false
2007-08-13 10:20:50.928817 12366 >> { ImbRFC822HeaderParser::parseLine , 17
2007-08-13 10:20:50.928836 12366 >> } ImbRFC822HeaderParser::parseLine , 54
2007-08-13 10:20:50.928844 12366 >> { ImbRFC822HeaderParser::getHeaderValueInternal , true
2007-08-13 10:20:50.928859 12366 >> } ImbRFC822HeaderParser::getHeaderValueInternal
2007-08-13 10:20:50.928890 12366 >> { ImbRFC822HeaderParser::checkForEndOfHeaders , 54
2007-08-13 10:20:50.928897 12366 >> } ImbRFC822HeaderParser::checkForEndOfHeaders , false
2007-08-13 10:20:50.928901 12366 >> { ImbRFC822HeaderParser::parseLine , 54
2007-08-13 10:20:50.928913 12366 >> } ImbRFC822HeaderParser::parseLine , 79
2007-08-13 10:20:50.928916 12366 >> { ImbRFC822HeaderParser::getHeaderValueInternal , true
2007-08-13 10:20:50.928924 12366 >> } ImbRFC822HeaderParser::getHeaderValueInternal
2007-08-13 10:20:50.928939 12366 >> { ImbRFC822HeaderParser::checkForEndOfHeaders , 79
2007-08-13 10:20:50.928943 12366 >> } ImbRFC822HeaderParser::checkForEndOfHeaders , false
2007-08-13 10:20:50.928951 12366 >> { ImbRFC822HeaderParser::parseLine , 79
2007-08-13 10:20:50.929172 12366 >> } ImbRFC822HeaderParser::parseLine , 203
2007-08-13 10:20:50.929180 12366 >> { ImbRFC822HeaderParser::getHeaderValueInternal , true
2007-08-13 10:20:50.929187 12366 >> } ImbRFC822HeaderParser::getHeaderValueInternal
2007-08-13 10:20:50.929199 12366 >> { ImbRFC822HeaderParser::checkForEndOfHeaders , 203
2007-08-13 10:20:50.929206 12366 >> } ImbRFC822HeaderParser::checkForEndOfHeaders , false
2007-08-13 10:20:50.929210 12366 >> { ImbRFC822HeaderParser::parseLine , 203
2007-08-13 10:20:50.929222 12366 >> { ImbHTTPHeaderParser::flavour
2007-08-13 10:20:50.929225 12366 >> } ImbHTTPHeaderParser::flavour
2007-08-13 10:20:50.929233 12366 >> } ImbRFC822HeaderParser::parseLine , 'THROW: Empty or invalid header name found at position', 2
03, 'HTTP'
2007-08-13 10:20:50.929264 12366 >> { ImbHTTPHeaderParser::flavour
2007-08-13 10:20:50.929271 12366 >> } ImbHTTPHeaderParser::flavour
2007-08-13 10:20:50.929286 12366 >> ImbRFC822HeaderParser::parseLine , 'Throwing exception', '/build/S600_P/src/WebServices/WSLibra
ry/ImbWSRFC822HeaderParser.cpp', 419, 'BIP3156', 'Empty or invalid header found at position: &1.', 203, 'HTTP' |
I'm still working on getting the header displayed from a utility.
_________________
Thanks!!!
Paul D |
|
| Back to top |
|
|
| Paul D |
| Posted: Mon Aug 27, 2007 5:50 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
We have the PMR open. We did find out from IBM that there is more checking done on the HTTP header now than in v5. We've sent in an ethereal trace to them that they are reviewing. We are having a hard time seeing exactly what's in the header that is the issue so I don't have anything to post yet on that.
_________________
Thanks!!!
Paul D |
|
| Back to top |
|
|
| Paul D |
| Posted: Tue Sep 04, 2007 11:28 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
We got a trace version of the data flow engine and have a full view of the whole header now. We've determined the the service (Siebel Workflow) is sending back a header field with a space in the name, which is not valid. Example of invalid HTTP response header field:
This validates Section 3.1 of RFC 822 of the spec. Broker is really working as expected. We are trying to change Siebel to get the header to be compliant.
_________________
Thanks!!!
Paul D |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
