# Direct access, you will get response header `Set-Cookie` with name `JSESSIONID`. curl -I --resolve acm.martian.tk:443:188.8.131.52 https://acm.martian.tk/CLanguage/images/rand.jpg # Via Cloudflare, upstream response header `Set-Cookie: JSESSIONID=...` missing curl -I --resolve acm.martian.tk:443:184.108.40.206 https://acm.martian.tk/CLanguage/images/rand.jpg
Just to be absolutely sure, you only have one single “acm” A record in your account and that account’s nameservers are “dawn” and “neil”. Right?
Any chance your server is - for whatever reason - not creating a session when the request comes from Cloudflare’s IP addresses? Have you double checked the session cookie gets sent in these cases too?
Yeah, only one A record of acm. And Proxy status is enabled now. Maybe I’ll disable it to make the service work as expect.
And the nameservers in your account also match those I mentioned?
No other NS records.
No, no, I meant the nameservers listed in your account on Cloudflare. Check on your DNS page if it mentions these very nameservers.
Same configuration on page https://dash.cloudflare.com/454adf2dc1dadad76bc8e6e8006c6a56/martian.tk/dns
In that case I can only suggest to open a support ticket. Maybe they can shed some light where that particular header vanishes.
I changed the issue body, this issue should only be related to the configuration of Cloudflare’s nginx, rather than the dns service.
No need to change the hosts file
# Via Cloudflare curl -I --resolve acm.martian.tk:443:220.127.116.11 https://acm.martian.tk/CLanguage/images/rand.jpg # Direct curl -I --resolve acm.martian.tk:443:18.104.22.168 https://acm.martian.tk/CLanguage/images/rand.jpg
I didnt say it was related to DNS, I wanted to check if you really are in the right account.
Anyhow, at this point you should open a support ticket.
Do I need to raise an issue anywhere else besides
community.cloudflare.com? What page should I go to?
You didnt raise an issue here. You simply opened a thread.
You need to open a ticket at support.cloudflare.com/requests/new
The current default cache policy caches some file extensions by default and it includes
jpg. Finally I resolve this issue by adding a custom page rule to process all requests with
Origin Cache Control: On.
This topic was automatically closed after 14 days. New replies are no longer allowed.