ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Message Broker SupportHow to accept Http 302 not found in HttpRequest Node

Post new topicReply to topic Goto page Previous  1, 2
How to accept Http 302 not found in HttpRequest Node View previous topic :: View next topic
Author Message
rekarm01
PostPosted: Mon Oct 29, 2012 12:18 am Post subject: Re: How to accept Http 302 not found in HttpRequest Node Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 1372

cooldudes wrote:
I tried by checking the [Follow] HTTP(s) redirection check box ...

Several others have asked about that already, but it does need to be checked.

cooldudes wrote:
... and still am getting the same error.

What error, exactly?

rekarm01 wrote:
Run a debug-level usertrace, and post the complete and exact error message, and where it occurs.

How's that coming along?

cooldudes wrote:
The flow is not going to out terminal. It is going to error terminal and the above trace log is for error node.

The node only generates an ExceptionList for the failure terminal, not for the out or error terminals. The Trace node output indicates there is no response message body; how does the error flow handle that case?

lancelotlinc wrote:
Since you are using SOAP, why did you select HTTPRequest node instead of SOAPRequest node?

Who said that the OP was using SOAP? Even if that's the case, how does the SOAPRequest node handle HTTP redirects?
Back to top
View user's profile Send private message
maesbrae
PostPosted: Wed Jun 18, 2014 3:07 pm Post subject: Reply with quote

Novice

Joined: 03 Jun 2003
Posts: 12

Apologies for resurrecting a 2 year old post but did you get to the bottom of this? Does the 'Follow HTTP(S) redirection' tick box have any effect? I just get an HTTP 302 output to the error terminal whether the box is ticked or not.
_________________
There are two ways to slide easily through life; to believe everything or to doubt everything. Both ways save us from thinking.
Back to top
View user's profile Send private message
harlando2
PostPosted: Wed Sep 09, 2015 9:59 am Post subject: Reply with quote

Newbie

Joined: 27 Sep 2006
Posts: 4

Hi

Just wondered if anybody has got to the bottom of this issue.
I also cannot get the http request node to manage a redirect.

"Follow HTTP(S) redirection" is checked and I have tried both HTTP1.0 and HTTP1.1 settings to no avail.
HTTP(S) proxy location is configured as I can't get to the web without it.
The destination is just HTTP, not HTTPS. I am aware of the following APAR (delivered in 9.0.03) which is triggered when HTTPS and a proxy are combined.
http://www-01.ibm.com/support/docview.wss?uid=swg1IT01504

When I point SOAPUI at the same destination as the HTTP request node with the same proxy, I can see that SOAPUI is dealing with the redirect request for me when using the "Fiddler" utility to see what is going on behind the scenes.

The versions of broker I have tested on are windows 32 bit as follows. Both exhibit exactly the same behaviour.

Fixpack capability level = 'all' (effective level '7.0.0.5')
Fixpack capability level = 'all' (effective level '9.0.0.2')

When running the interactive debugger, the HTTP 302 response comes out of the HTTP request error terminal as shown below. I have manually anonymised part of the URI.
There is also no exception.

HTTPResponseHeader
X-Original-HTTP-Status-Line:CHARACTER:HTTP/1.1 302 Found
X-Original-HTTP-Status-Code:INTEGER:302
Cache-Control:CHARACTER:private,no-cache
Pragma:CHARACTER:no-cache
Content-Length:CHARACTER:229
Content-Type:CHARACTER:text/html; charset=utf-8
Expires:CHARACTER:-1
Location:CHARACTER:/(S(vbrrrtxbmwra0gb435gentff))/ws/<Manually anonymised>/download.aspx?cf=7&references=12920&views=64&lang=en Server:CHARACTER:Microsoft-IIS/7.5
X-Powered-By:CHARACTER:ASP.NET
Date:CHARACTER:Wed, 09 Sep 2015 17:18:37 GMT
Connection:CHARACTER:close

As a workaround, I have had to attach a compute node and a second http request node to the error terminal of the original http request node.

Will look into raising a PMR and trying out 9.0.0.3 if I get no response from here. I'm pinned back to 9.0.0.2 at present.

Kristian
_________________
Kristian

Environment
---------------
AIX 5.2.0.0
V6 brokers at CSD2
Win 2000 Config manager at CSD2
WIN xp desktop at CSD2
Back to top
View user's profile Send private message Send e-mail
mgk
PostPosted: Wed Sep 09, 2015 8:00 pm Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1591
Location: IBM Hursley, UK

The most likely reason for a redirection not working is that there is no "Location" header in the response, or that the "Location" header is not a valid URL. I can see you have a "Location" header, and that does not look like a valid "http://" or "https://" URL.

Kind regards,
_________________
MGK
IBM Global Blockchain Enablement
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Thu Sep 10, 2015 4:34 am Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

mgk wrote:
The most likely reason for a redirection not working is that there is no "Location" header in the response, or that the "Location" header is not a valid URL. I can see you have a "Location" header, and that does not look like a valid "http://" or "https://" URL.


Which points the finger solidly at the proxy server.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
rama91
PostPosted: Wed Oct 02, 2019 10:48 pm Post subject: Reply with quote

Novice

Joined: 28 Aug 2019
Posts: 12

Apologies for resurrecting an old Post. Did you manage to get to the bottom of this issue. I'm facing a similar situation where Soaprequest node is unable to handle https redirect. The backend proxy server responds with HTTP 302 with new URL populated in location header,but soaprequest node is unable to resend request.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum IndexWebSphere Message Broker SupportHow to accept Http 302 not found in HttpRequest Node
Jump to:



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
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.