Getting "Connection Reset" error instead of 401 on multipart HTTP

, , , , ,
1

10.15

Hi,

I am making a multipart HTTP call with a Bearer Token. When I use the right token I don’t have any problems. I can send a pdf file with that call.

My problems start if I use the wrong Bearer Token. Everything works normally if I send a request with the wrong Token via Postman. I can see the HTTP code as 401, the response as JSON, and also header values without an issue.

PostmanResponseHeader
PostmanResponseHeader2132×537 54.6 KB

When I make the same request from 10.15 webMethods server via “pub.client:http” it throws “com.wm.net.NetException: [ISC.0064.9306] Connection was closed during read” or “com.wm.app.b2b.server.ServiceException: java.net.SocketException: Connection reset” error.

I changed the log level to “Trace” for Integration Server and attached the related piece of logs here.
server.log (11.1 KB)

As I understand from the logs, I am getting 401 in the first place but then the webMethods server makes another call, this time it uses NTLM for authorization then it gets 401 again but this time I see WWW-Authenticate: NTLM in the response header and probably it causes the issue.

I am unsure why it retries after it gets 401 and where this NTLM is coming from. I can provide further info if needed.

Are there any suggestions to solve this?

Many thanks in advance.

2

Your query is not pretty clear, but check out this setting if it makes some difference.

watt.net.http401.retryWithoutCookie

Controls whether Integration Server retries HTTP requests without a cookie header. Set the parameter to false to prevent the pub.client:http service from retrying a request without a cookie header when Integration Server receives HTTP 401 as the response. The default is true.

Note:
The watt.net.http401.retryWithoutCookie parameter is introduced for PIE-76895 in IS_10.15_Core_Fix1.

3

Hi Sandeep,

Thanks for your answer. I set “watt.net.http401.retryWithoutCookie” as false but the result is the same. I also set false to " watt.net.http401.throwException" to disable getting exceptions after I got 401 but it also didn’t help.

Regards,
Mustafa

4

service: pub.client:http has parameter of: followRedirect
try to use no when you call it.

1 Like