|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Unwanted HTTP header |
« View previous topic :: View next topic » |
Author |
Message
|
chetu777 |
Posted: Mon Aug 05, 2013 10:52 pm Post subject: Unwanted HTTP header |
|
|
Acolyte
Joined: 07 Sep 2009 Posts: 59
|
Hi All,
I am using a HTTP resuqest/response flow. Input is a GET method and output is a CSV data (which is extracted from the DB).
I am supposed to use HTTPs protocol for this service.
When I hit my service I am able to get the response on a browser with values, but there is also a header by default which is unwanted.
Can you kindly let me know how to remove this?
[quote]The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
--------------------------------------------------------------------------------
Invalid at the top level of the document. Error processing resource 'https://stgesvtst.xyz.com/xyz/labelnum...[/quote]
Note : In HTTP relpy node, I have even removed selection of "Generate default HTTP headers frpm response"
Previous requirment was to use HTTP protocol and I was able see proper response without any headers in my browser, but when I selected HTTPs protocol, the headers are getting generated.
Thanks in advance.[/quote] |
|
Back to top |
|
 |
goffinf |
Posted: Mon Aug 05, 2013 11:56 pm Post subject: Re: Unwanted HTTP header |
|
|
Chevalier
Joined: 05 Nov 2005 Posts: 401
|
chetu777 wrote: |
... Input is a GET method and output is a CSV data (which is extracted from the DB).
Quote: |
The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
--------------------------------------------------------------------------------
Invalid at the top level of the document. Error processing resource 'https://stgesvtst.xyz.com/xyz/labelnum... |
|
[/quote]
You don't say what HTTP response header is causing the problem, but if I were to guess, it is probably Content-Type and you have probably set it (or left it defaulting) to text/XML ??
Since you started out by saying your GET response returns CSV data why would you be surprised that the default XSLT style sheet that your browser is using can't serialise the content ?
Suggest you explicitly set the HTTP Content-Type response header in your flow to text/plain or similar.
Fraser. |
|
Back to top |
|
 |
mqsiuser |
Posted: Tue Aug 06, 2013 2:03 am Post subject: Re: Unwanted HTTP header |
|
|
 Yatiri
Joined: 15 Apr 2008 Posts: 637 Location: Germany
|
Probably you are copying InputRoot to OutputRoot?
Do that, but don't forget to NULL-out the HTTP-Request-Header:
Something like "SET OutputRoot.HttpHeader = NULL;" _________________ Just use REFERENCEs |
|
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
|
|
|
|