iOS 6 Bug: Safari caches POST requests

[KevMo]

I'm not sure how many people this will affect, but I thought I would send out a heads up. Check out these posts for more information:

http://stackoverflow.com/questions/12506897/is-safari-on-ios-6-caching-ajax-results

http://www.devthought.com/2012/09/22/understanding-the-ios6-ajax-bugs/

[Jens]

Thanks. Good to know.

-- J.

[Christian Kuetbach]

Implement a Header-Filter:

public class HeaderFilter implements Filter {

public void destroy() {
}

public void doFilter(ServletRequest req, ServletResponse res,
FilterChain filterChain)
throws IOException, ServletException {

HttpServletResponse response = (HttpServletResponse) res;
response.addHeader("Cache-Control", "no-cache");
filterChain.doFilter(req, res);
}

public void init(FilterConfig arg0) throws ServletException {
}

}


If you set this filter to filter all your reqests to your dispatch-servlet,
no results should be cached.


Regards,
Christian Kuetbach

[Nicolas Hoby]

Works perfect, thank you!

Just for completion, to install the filter add the following to your
Web.xml:

<filter>
<filter-name>HeaderFilter</filter-name>
<filter-class>server.services.HeaderFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>HeaderFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>

[Jeffrey Roe]

So this will cause all files to be downloaded over and over again.
Is there a way to do this fix just for IOS devices.
Jeffrey Roe,

> --
> You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
> To post to this group, send email to google-we...@googlegroups.com.
> To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
>

[Jamie]

You could write the filter to only affect POSTs

Or, you could configure the filter mapping to only apply the filter to your Servlet(s).

Jamie.

> To unsubscribe from this group, send email to google-web-toolkit+unsub...@googlegroups.com.

[Joseph Lust]

Of course you can just do this for iOS devices. Just parse the UserAgent parameter from the request.

Sincerely,

Joseph

[Rob Whiteside]

We came across this problem too, I was banging my head against the wall for hours.

I see some others solved it with filters, if you use apache you can mess with the headers via the Headers Module.  Add the following to the httpd.conf:

LoadModule headers_module modules/mod_headers.so

.......

<Location /yourgwtapp/gwtRequest>

Header set Cache-Control no-cache

</Location>

That will add set the headers for any response at that location.  For us, that was the GWT Request Factory endpoint.

[Óscar Frías Barranco]

Hello.

We just override the method onAfterResponseSerialized from RemoteServiceServlet in the RPC services implementation and this fixes this issue:

    @Override
    protected void onAfterResponseSerialized(String serializedResponse) {
        HttpServletResponse response = getThreadLocalResponse();
        response.setDateHeader("Expires", 0L);  // always expired
        response.setHeader("Cache-Control", "no-cache");
    }

Regards,
Oscar



El domingo, 23 de septiembre de 2012 10:10:35 UTC+2, Rui Oliveira escribió:

Hi,

Whats the best away to solve this issue? I have hundreds of RPC and I'm looking for a global way to change the header to no-cache.

Sincerely

Rui