Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

HTTP Status Code 204 on an HTTP Send Port

94 views
Skip to first unread message

Christian Loris

unread,
May 8, 2008, 4:54:00 PM5/8/08
to
What is the expected behaviour when you send a message on an http send port
and the response is a 204?

I get the following error when the message suspends:

Error Code: 0xc0c0167a (Transmission Failure)
The server committed a protocol violation. Section=ResponseHeader Detail=CR
must be followed by LF

The response from the web server looks like this:

Frame:
+ Ethernet: Etype = Internet IP (IPv4)
+ Ipv4: Next Protocol = TCP, Packet ID = 51382, Total IP Length = 418
+ Tcp: Flags=...PA..., SrcPort=HTTP(80), DstPort=2039, Len=378,
Seq=1915624311 - 1915624689, Ack=899843955, Win=64240 (scale factor not found)
- Http: Response, HTTP/1.1, Status Code = 204
- Response:
ProtocolVersion: HTTP/1.1
StatusCode: 204, No content
Reason: No Content
Date: Thu, 08 May 2008 20:46:50 GMT
Server: Microsoft-IIS/6.0
XPoweredBy: ASP.NET
user-agent: Microsoft (R) BizTalk (R) Server 2006 3.0.1.0
datahandlingsubsystem: HRFQADPriceListInbound
transporttype: HTTP
expect: 100-continue
connection: Keep-Alive
cache-control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Host: mlbsbltst1vm
HeaderEnd: CRLF

Raw data if interesetd:

00 50 56 A3 21 98 00 50 56 88 24 6B 08 00 45 00 01 A2 C8 B6 40 00 80 06 68
65 89 ED 5A 1A 89 ED 5A 45 00 50 07 F7 72 2E 1B 77 35 A2 87 73 50 18 FA F0 A3
2D 00 00 48 54 54 50 2F 31 2E 31 20 32 30 34 20 4E 6F 20 43 6F 6E 74 65 6E 74
0D 0A 44 61 74 65 3A 20 54 68 75 2C 20 30 38 20 4D 61 79 20 32 30 30 38 20 32
30 3A 34 36 3A 35 30 20 47 4D 54 0D 0A 53 65 72 76 65 72 3A 20 4D 69 63 72 6F
73 6F 66 74 2D 49 49 53 2F 36 2E 30 0D 0A 58 2D 50 6F 77 65 72 65 64 2D 42 79
3A 20 41 53 50 2E 4E 45 54 0D 0A 75 73 65 72 2D 61 67 65 6E 74 3A 20 4D 69 63
72 6F 73 6F 66 74 20 28 52 29 20 42 69 7A 54 61 6C 6B 20 28 52 29 20 53 65 72
76 65 72 20 32 30 30 36 20 33 2E 30 2E 31 2E 30 0D 0A 64 61 74 61 68 61 6E 64
6C 69 6E 67 73 75 62 73 79 73 74 65 6D 3A 20 48 52 46 51 41 44 50 72 69 63 65
4C 69 73 74 49 6E 62 6F 75 6E 64 0D 0A 74 72 61 6E 73 70 6F 72 74 74 79 70 65
3A 20 48 54 54 50 0D 0A 65 78 70 65 63 74 3A 20 31 30 30 2D 63 6F 6E 74 69 6E
75 65 0D 0A 63 6F 6E 6E 65 63 74 69 6F 6E 3A 20 4B 65 65 70 2D 41 6C 69 76 65
0D 0A 63 61 63 68 65 2D 63 6F 6E 74 72 6F 6C 3A 20 6E 6F 2D 63 61 63 68 65 2C
20 6D 75 73 74 2D 72 65 76 61 6C 69 64 61 74 65 2C 20 6D 61 78 2D 61 67 65 3D
30 0D 0A 70 72 61 67 6D 61 3A 20 6E 6F 2D 63 61 63 68 65 0D 0A 68 6F 73 74 3A
20 6D 6C 62 73 62 6C 74 73 74 31 76 6D 0D 0A 0D 0A

.PV£!˜.PVˆ$k..E..¢È¶@.€.he‰íZ.‰íZE.P.÷r..w5¢‡sP.úð£-..HTTP/1.1 204 No
Content..Date: Thu, 08 May 2008 20:46:50 GMT..Server:
Microsoft-IIS/6.0..X-Powered-By: ASP.NET..user-agent: Microsoft (R) BizTalk
(R) Server 2006 3.0.1.0..datahandlingsubsystem:
HRFQADPriceListInbound..transporttype: HTTP..expect:
100-continue..connection: Keep-Alive..cache-control: no-cache,
must-revalidate, max-age=0..pragma: no-cache..host: mlbsbltst1vm....

Any help would be appreciated.

--
Christian Loris
http://www.implementsivillage.net

Thiago

unread,
May 9, 2008, 4:29:05 PM5/9/08
to
Hi Christian,

I belive a 204 response means the response has "No Content", that is, the
response body is empty. Are you expecting some data back?

Thiago Almeida
http://connectedthoughts.wordpress.com

Christian Loris

unread,
May 15, 2008, 1:00:05 PM5/15/08
to
No content was expected. Just a 200 family reply to affirm receipt and
successful processing.

Christian Loris

unread,
May 15, 2008, 3:22:01 PM5/15/08
to
I found out what was wrong. First, I posted the wrong response message. The
response message we are getting is similar to the one above. But the
problematic header has a couple of additional custom fields in it. One of
the fields of note was:

object id: blahblah

After reviewing RFC 2616, it turns out that the heade field names must be
tokens. This means NO SPACES! The space in between object and id is causing
BizTalk to choke. Getting the owners of the web service to fix this. If
this is not the problem, I will follow up here.

0 new messages