| Author |
Message
|
| next |
 Posted: Thu Jul 22, 2010 3:33 pm Post subject: Any restrictions on the Http Request node RequestURL?? |
 |
|
Voyager
Joined: 02 May 2010
Posts: 75
|
Hi,
Can anybody let me know if there are any restrictions on sending an xml message via OutputLocalEnvironment.RequestURL??
I am doing something like this
SET OutputRoot.HTTPRequestHeader.POST = 'servlets-examples/servlet/TestServlet?';
SET OutputRoot.HTTPRequestHeader.Host = 'http://remotehost:8080';
SET OutputRoot.HTTPRequestHeader."Content-Type" = 'application/x-www-form-urlencoded';
SET OutputLocalEnvironment.Destination.HTTP.RequestLine.Method = 'POST';
SET OutputLocalEnvironment.Destination.HTTP.RequestLine.RequestURL = 'https://remotehost:8080/servlets/TestServlet?<xml message/>'.
If the message is small, it is working fine and the request is reaching the target servlet.But when the message is huge, the request doesnt reach the servlet at all... I am stuck with this. Any help is highly appreciated...  |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Jul 22, 2010 5:46 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
What does the HTTP standard say is the maximum length of a URL?
What does service provider you are trying to call say about this? |
|
| Back to top |
|
|
| next |
| Posted: Fri Jul 23, 2010 1:42 am Post subject: |
|
|
Voyager
Joined: 02 May 2010
Posts: 75
|
I am not able to find any standards regarding this. When i googled, i found that POST method doesnt have any limitations of size as such.
The service providers say that other applications are able to call their service using POST method.
So they are telling broker is the culprit.  |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 23, 2010 2:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Them saying that other people are able to call their service just fine has nothing to do with whether other people are able to call their service just fine with an URL as large as you are trying to create.
Unfortunately right now, you can't necessarily get a good clear trace of the HTTP communications in and out of Broker without actually using a packet sniffer or etc. to watch the traffic.
If that doesn't show that Broker is establishing the network connection in the first place, then open a PMR. |
|
| Back to top |
|
|
| Amitha |
| Posted: Fri Jul 23, 2010 7:26 am Post subject: |
|
|
Voyager
Joined: 20 Nov 2009
Posts: 80
Location: Newyork
|
As mqjeff suggested, try to get the packets exchanged.
you can use TCP/IP monitor available in Eclipse to see the message exchange. |
|
| Back to top |
|
|
|
|
