Android Question Setting cookies for an HttpJob doesn't work for seemingly no reason.

[Yuri Cinesi]

Here is what I'm basically doing: I check if a text file containing the stored cookies exists, if it doesn't then I use webviewextra to run some javascript on the login page and log in. Following that I use cookiemanager to extract the cookies and save them to the aforementioned file.
If the file does exist then an HttpJob is defined and I use Job.GetRequest.SetHeader("Cookie",File.Readstring(File.DirInternal,"LoginCookies") to read the file and add the cookies to the httpjob. Of course that line is after the download.

Now here's the tricky part. The code that handles getting the cookies works perfectly fine. However in my main project the cookies don't work. When I tried creating a smaller project to reproduce the bug I was unable to, despite the code handling the cookies being identical.

I have no clue why this happens. I've tried clearing the header - it did nothing. I have also tried clearing the project.

I'm honestly at a loss on this issue. Every variable is, as far as I can tell, the same between the actual project and the test case. Same page, same login, same download method. Any help would be GREATLY appreciated.

 

[Erel]

You can see the request cookies with the debugger. The request object name is 'req'. Check the request cookies in JobDone and see whether you find the cookie you set.

 

[Yuri Cinesi]

I can indeed find it. It seems to be correctly updated and everything. It still doesn't work.

The exact same cookie header however, when used in the other application, works just fine. I'm at a loss.

 

[Erel]

Make sure that there is no extra space or something similar.

 

[Yuri Cinesi]

There is not.

 

[OliverA]

For my clarification, what does not work in the larger application? Getting the cookies and storing them in a file or reading the cookies from a file and using them to create another GET request (via download() method)?

 

[Yuri Cinesi]

Getting cookies works perfectly fine. The issue is that despite me applying them to the httpjob and them showing up in the debugger the job doesn't authenticate correctly. I'm checking for a specific string that only shows up if the user is logged in which is how I know.

 

[OliverA]

Are you in control of the receiving application? What does it get? Any cookies at all?

 

[Yuri Cinesi]

I am sadly not in control of the receiving application. It's a website I don't control.
As far as B4A is concerned though the cookies are there.

 

[OliverA]

You need something to capture the outgoing traffic to the website. Something like https://www.wireshark.org/. Then you can see if the cookies are sent out to the website.

 

[Yuri Cinesi]

I've got wireshark already, but I'm not sure how to capture the traffic from my phone as I'm using a physical device

 

[OliverA]

Try this url in your code. Just make sure you're not using a cookie file that has valid login information. See if the cookies go out. Please, only change the URL and scramble the cookies in the file (don't add or delete). See if it sees the cookie header. Note: I have never used this site, I just googled for something easier than WireShark.

URL: https://request.urih.com/

 

[OliverA]

What version of B4A? Are you using the standard libraries for HTTP access? Which ones? Are you using a modified version of the libraries (by including the class libraries)?

 

[Yuri Cinesi]

I'm using the standard versions of the OkHttpUtils2 and OkHttp libraries.

 

[Yuri Cinesi]

It does show up. What the actual...?

 

[OliverA]

Copy the cookies from the site to notepad. Repeat the experiment with your working test version with that url and see if you see any anomalies/differences in the cookies.

 

[Yuri Cinesi]

I honestly can't find anything. In the main app the cookies seem correct as far as I can tell, yet it doesn't work with the actual website.

 

[OliverA]

The same cookies, the exact same cookies work with the test application and the real website but not with the big application and the real website? URLs are the same, cookies are the same, etc site from which cookies come is the same...

 

[Yuri Cinesi]

Everything is identical. I copy the exact same cookies and use them in the test application and they work. The URL is the same and all that jazz.
If you'd like I can change share the application via PMs. I'll change the login details so that I don't give you the password I usually use but it's not like you can actually do anything with that account. It's just a testing one so it has no permissions.

 

[OliverA]

What is the response from the server?