Cookie problems with v 1.29

["Ian Patterson" <ian@xxxxxxxxxxxxxxxxx>]

iSeries V5R1
Using SSL (TLS1.0)
HTTPAPI v 1.29

We were using V1.20 for many years without issues.
I have upgraded to 1.29 and having problems communicating with the remote
server.

The TLS1.0 session is established OK.
In the original program, we determined the cookie by checking for JSESSIONID
in the first HTTP header received from the server, then used this in
subsequent sessions.

With 1.29 something has changed, and the symptoms point to the cookie
handling.

This is part of the log where it goes wrong:

Protocol Used: TLS Version 1.0
http_persist_post(): entered
http_persist_req(POST) entered.
http_long_ParseURL(): entered
do_oper(POST): entered
There are 1 cookies in the cache
POST /ss02/submissions/submission-webapp/authenticateApp.do HTTP/1.1
Host: testservices2.bacs.co.uk
User-Agent: 1000
Content-Type: text/xml
Content-Length: 4253
Cookie: $Version=0;
JSESSIONID=D3GKV2sZLnLKkMSpfLyhVZgyWyY9LG6f1LnpzR34QX9YCyWyGPnw!-1936789723!
wls-baap401.test.vocalink.co.uk!13129!13109; $Path=/;
cookie:
JSESSIONID=D3GKV2sZLnLKkMSpfLyhVZgyWyY9LG6f1LnpzR34QX9YCyWyGPnw!-1936789723!
wls-baap401.test.vocalink.co.uk!13129!13109; path=/
Connection: close

Note that there are two lines with cookie info.

Does anyone know which cookie is being sent at this point in the POST?
The second cookie line is what is expected by the server.

 
Regards
 
Ian Patterson
 

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------