Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Cache-Control makes trouble in Titanium #124

Closed
PayteR opened this Issue Nov 19, 2012 · 7 comments

Comments

Projects
None yet
4 participants

PayteR commented Nov 19, 2012

Hello, im just making app in Titanium, and have problem with display image on first time in imageView. Problem occurrs only first time when thumb is generated, when cached image is loaded its everything fine. I spend lot of time to get solution, and its this:

$response->headers->remove('Cache-Control');

Somehow Cache-control header is problem there, so should be gone, can you add somewhere this code? thx

Owner

lsmith77 commented Nov 19, 2012

well you could add this by extending the controller. but i am not quite sure why there is an issue ..
can you show me what headers you are seeing without adding this method call?

PayteR commented Nov 19, 2012

im pretty sure that this is problem, when its there Cache-Control no-cache then its not shown, all headers are here:

Cache-Control no-cache
Connection close
Content-Type image/png
Date Mon, 19 Nov 2012 22:59:16 GMT
Server Apache/2.4.2 (Win32) OpenSSL/1.0.1c PHP/5.4.4
X-Powered-By PHP/5.4.4
x-debug-token 50aab9c68889f

PayteR commented Nov 20, 2012

i have fix this by extending controller, so for me its fine now... i dont know if you want to add it there, anyway, this thread can help to someone with this issue... you can close it, thx

Owner

lsmith77 commented Nov 20, 2012

setting Cache-Control no-cache is the default behavior in Symfony2 when no cache headers are set explicitly. so actually i would expect Symfony2 to readd that header even if you remove it, seems like it doesnt though .. can you also paste what header you are seeing now?

PayteR commented Nov 20, 2012

now its same headers without that Cache-Control no-cache, its weird, but its true, now that images are shown

@PayteR could you please test the patch in #6037 to see if that would fix the issue for you?

If not, is there some way for me to reproduce the issue?

Thanks!

Contributor

havvg commented Feb 13, 2013

@PayteR Did you test the patched version?

@havvg havvg closed this Mar 13, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment