| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 400 Bad Request when submitting xml files via proxy |
« View previous topic :: View next topic » |
| Author |
Message
|
| abd.wsu |
 Posted: Thu Aug 13, 2015 5:42 pm Post subject: 400 Bad Request when submitting xml files via proxy |
 |
|
Acolyte
Joined: 12 Sep 2012
Posts: 65
|
Hello,
we recently migrated from MB7006 to IIB9003 running on RHEL6.5. After the migration we are seeing an issue with one flow which uses a http request node to push xml messages to various US state websites via a proxy server.
We are seeing 400 Bad Request errors for 2 of the 14 states we file with.
I checked the ssl certs and keystore locations. Everything looks good. Turned on the jsse traces and the service traces.
Nothing in registered in the jsse trace and the service trace shows the ssl handshake is happening.
I openned a PMR with IBM and they looked at the entire setup, flow, traces and responded saying everything looks good. However, I had a doubt these two states were using a more secure cipher with TLS and asked IBM to look into it.
I found out there are a number of ciphers that are disabled by default in the jsse libs.
After some guidance from IBM i was able to enable the disbaled ciphers, but that didn't help either. We still see 400 Bad Request errors. Actually, one state was working fine after the migration, but started giving this error after they moved their url.
Should i look into the proxy as a possible cause to the issue? Is there anything i am missing?
Please help. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Aug 14, 2015 4:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Bad request usually indicates an issue with the content of the message, I thought.
https://www.flickr.com/photos/girliemac/sets/72157628409467125
Did you confirm that the other sides didn't change their APIs at least slightly?
On the off chance, did you make sure to recreate your security profiles and ... the other profile thingys...  [/url] |
|
| Back to top |
|
|
| abd.wsu |
| Posted: Fri Aug 14, 2015 7:33 am Post subject: |
|
|
Acolyte
Joined: 12 Sep 2012
Posts: 65
|
| We hadn't setup anything for security profile in MB7. Would it matter? I had done some research on setting up security profile but didn't pay much attention to it since we were not using it in MB7. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 14, 2015 9:36 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If you didn't set any of those, then it probably doesn't contribute to the problem.
It was more or less a random thought.
You should check with the receivers to see why the bad request is being produced. |
|
| Back to top |
|
|
| abd.wsu |
| Posted: Thu Aug 20, 2015 11:52 am Post subject: |
|
|
Acolyte
Joined: 12 Sep 2012
Posts: 65
|
| Looks like it has nothing to do with the SSL or the cipher suites. It appears the reciever side changed their url pages without prior notice. We are altering our xml format and modifying the xsl style sheets to match what they want. |
|
| 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
|
|
|
|
