Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

[16:08:38 CST(-0600)] <prairycat> https://speakerdeck.com/jaffathecake/application-cache-douchebag

[16:10:05 CST(-0600)] <drewwills> and render/resource URLs seem to have nice features for setting response headers to instruct browsers on appropriate caching

[16:10:12 CST(-0600)] <drewwills> but not action

[16:10:21 CST(-0600)] <EricDalquist> right

[16:10:31 CST(-0600)] <EricDalquist> because the browser should never cache them

[16:10:34 CST(-0600)] <EricDalquist> since they return 302s

[16:10:40 CST(-0600)] <EricDalquist> which by the http spec are uncachable

[16:10:50 CST(-0600)] <drewwills> hmmm

[16:11:41 CST(-0600)] <EricDalquist> http://code.google.com/p/chromium/issues/detail?id=103458

[16:11:42 CST(-0600)] <EricDalquist> hrm

[16:11:51 CST(-0600)] <EricDalquist> wonder if it is a long standing chrome bug ...

[16:12:19 CST(-0600)] <EricDalquist> guess would could add a random param to action urls (tongue)

[16:12:33 CST(-0600)] <EricDalquist> it would be nice if chrome just didn't be bad

[16:12:59 CST(-0600)] <EricDalquist> could you capture the raw response from the chrome dev tools

[16:13:14 CST(-0600)] <EricDalquist> so we can see if any cache headers are being set?

[16:16:49 CST(-0600)] <drewwills> i'm not sure I can... when it was doing it, there was no entry on the list to click on to view headers

[16:17:01 CST(-0600)] <drewwills> i might be able to get at that in a JS debugger

[16:17:47 CST(-0600)] <EricDalquist> http://www.charlesproxy.com/

[16:17:49 CST(-0600)] <EricDalquist> give that a try

[16:17:54 CST(-0600)] <EricDalquist> it works in free mode

[16:18:01 CST(-0600)] <EricDalquist> but is honestly worth the license cost

[16:18:13 CST(-0600)] <EricDalquist> it will sit between your browser and the server

[16:18:17 CST(-0600)] <EricDalquist> and logs everything

[16:20:53 CST(-0600)] <drewwills> bookmarked

[16:49:31 CST(-0600)] <jwennmacher> Should I just use UP jira for the issueManagement section of the maven plug-in for now or do you want another jira indicated?

[16:50:23 CST(-0600)] <EricDalquist> you can just refernce UP for now

[16:50:28 CST(-0600)] <EricDalquist> we'll get a new jira setup for it soon