I have a Page A which redirect me on an other page (page B) where i can edit a record from my DB. When i submit the form, DB is updated and i stay on the same Page B with a flash message. It's ok it works fine :)
I also have a "Leave" button to come back to Page A, see code below :
When i click on this link, the link works but it's like i got redirected back on PAGE A, datas are not refreshed... I have to hit F5 to see any change :(
If it can help, i also saw today an old flash message... I've checked and flash_auto_expire is set to true.
I don't know what to do, maybe i've missed somthing on my route config ?
And no caching proxy in the path (local or from your ISP). Or maybe the production webserver has very agressive caching headers, so the browser caches stuff it shouldn't?
Even a browser cache should not show an old page on a redirect, redirects are new URL requests.
I'm looking in this direction, the app is behind a first public website which uses APC and Gzip... I still don't understand why when i click on a link i have old datas and when i press F5 i got fresh datas :(
It's getting weider and weirder, if i test the route news/liste i got old values. If i test the route news/liste/ i get semi news values. Even weirder, on firefox i can't access the route, i got redirected on main page every time...
hmm... sounds like you have a challenge on your hands...
You say "/new/liste" and "/news/liste/" produce different results? If so, then it's definitely something outside the applications control, as Fuel strips the trailing slash, so for Fuel both are the same.
I suggest you get an HTTP request analyzer running (firebug, http-headers plugin, even wireshark), and check which requests go out to the server, what comes back, and what are the HTTP headers of the request and responses...