[Android] Image loading request is performed without cookie which was set earlier by "SetCookie" header of response

Description

1. I have a server which returns image only if request has authorization cookie.
2. I authorise on this server and get a HTTP response with Set-Cookie header with cookies in content.
3. Then I show an Image with URL pointing to this server. Image is failed to load. Same thing works OK on iOS.

I checked the network traffic, and found this:

1. Response which sets the cookie looks like this:

HTTP/1.1 200 OK
Server: nginx
Date: Sat, 22 Apr 2017 16:43:31 GMT
Content-Type: application/json;charset=utf-8
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Set-Cookie: JSESSIONID={Censored};Path=/somepath;Secure;HttpOnly
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Access-Control-Expose-Headers: Location
Cache-Control: no-cache, no-store, no-transform, must-revalidate
Vary: Accept-Encoding, User-Agent
Content-Encoding: gzip
Strict-Transport-Security: max-age=31536000; includeSubdomains;
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Connection: Keep-alive

1. Regular fetch-drived network requests after this are performed with this cookie:

GET {Censored/some url} HTTP/1.1
content-type: application/json
accept: application/json, text/plain, */*
authorization: {Censored}
Host: {Censored}
Connection: Keep-Alive
Accept-Encoding: gzip
Cookie: JSESSIONID={Censored/HERE IT IS!!}
User-Agent: okhttp/3.4.1

1. Image requests are performed without this cookie:

GET {Censored}/_persistent/project-diff.png?file=96-37&c=false HTTP/1.1
Host: {Censored}
Connection: Keep-Alive
Accept-Encoding: gzip
User-Agent: okhttp/3.4.1

Solution

The code which loads image should respect that cookie set before.

Additional Information

• React Native version: 0.43.4
• Platform: Android 7.1
• Development Operating System: macOS Seems similar to https://github.com/facebook/react-native/issues/6316 but on Android.

[andrey-skl]

Sadly that’s the way how react-native evolves: it doesn’t care about great bunch of small but breaking stuff issues there and there. Will it get some kind of polishing and bugfixing eventually? Nobody knows 😞

[ghost]

Does not work in 0.56.0 as well.