Header Fields not picked in Http Adapter

[Former Member]

Hi ,

I am sending a few custom header fields that have been set up in the HTTP adapter but for some reason they are not picked.

Any suggestions..

-Teresa

[Former Member · Accepted solution]

Hi,

Maybe the note 782220 will help you.

Regards,

Sameer

[Former Member · Accepted solution]

Thanks Sameer,

This note did help us pick up the header fields but on picking up it returns the header fields in lower case instead of the case Sensitive format I sent it in ..I looked at the trace log too and its in case sensitive format but when my 3rd party receives it, it is in lower case format...funny even the <?xml version="1.0" encoding="utf-8" standalone="yes" ?>

is also in lowercase..I am running XI 3.0 SP4..Is it an XI issue or something to do with my integration server which processes my HTTP adapter??? Or any other notes also needs to be applied??

Please help..

Trace level="1" type="T">---- Plain HTTP Adapter Outbound----</Trace>

<Trace level="1" type="T">----

---

</Trace>

- <Trace level="1" type="B" name="CL_HTTP_PLAIN_OUTBOUND-ENTER_PLSRV">

<Trace level="3" type="T">Quality of Service EO</Trace>

<Trace level="1" type="T">Get XML-Dokument from the Message-Objekt</Trace>

<Trace level="3" type="T">URL http://xkqbdev.ampton.net:50080/abc/Web/servlet/XMLChannelServlet</Trace>;

<Trace level="3" type="T">Proxy Host: 10.69.14.98</Trace>

<Trace level="3" type="T">Proxy Service: 80</Trace>

<Trace level="3" type="T">Authorization: Basic NDQ0NDQ0NDQ0OjQ0NDQ0NDQ0NA==</Trace>

<Trace level="3" type="T">~request_method POST</Trace>

<Trace level="3" type="T">~server_protocol HTTP/1.0</Trace>

<Trace level="3" type="T">accept: /</Trace>

<Trace level="3" type="T">content-type: text/xml</Trace>

<Trace level="3" type="T">Header-Fields</Trace>

<Trace level="3" type="T">X-Extricity-Sender-ID 444444444</Trace>

<Trace level="3" type="T">X-Extricity-BO-Type-ID http://xml.cXML.org/schemas/cXML/1.2.011/cXML.dtd</Trace>;

<Trace level="3" type="T">Prolog conversion Codepage: UTF-8</Trace>

<Trace level="3" type="T">Epilog conversion Codepage: UTF-8</Trace>

<Trace level="3" type="T">content-length 3023</Trace>

<Trace level="2" type="T">HTTP-Response :</Trace>

<Trace level="2" type="T">Code : 500</Trace>

<Trace level="2" type="T">Reason: Internal Server Error</Trace>

<Trace level="2" type="T">Code : 500</Trace>

<Trace level="2" type="T">Reason: Internal Server Error</Trace>

</Trace>

</Trace>

-Teresa

[Former Member · Accepted solution]

Hej,

We have the same issue regarding the Header Field and the HTTP adapter.

But there is an standards problem, not a tecnology problem. The standard for the HTTP protocol describes http header field names as case insensitive.

http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html

“4.2 Message Headers

HTTP header fields, which include general-header (section 4.5), request-header (section 5.3), response-header (section 6.2), and entity-header (section 7.1) fields, follow the same generic format as that given in Section 3.1 of RFC 822 [9]. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. “

Therefore, the application handling the message should not apply case sensitivity when receiving the message.