...
[16:03:22 CST(-0600)] <EricDalquist> and how is it being called?
[16:04:08 CST(-0600)] <drewwills> like this: https://gist.github.com/drewwills/4948781
[16:04:53 CST(-0600)] <EricDalquist> and the browser was only actually invoking the url once?
[16:05:00 CST(-0600)] <drewwills> the cache: false was a stap at correcting it... it's not proper and i took it out
[16:05:11 CST(-0600)] <EricDalquist> what browser is this?
[16:05:13 CST(-0600)] <drewwills> if i hit F5 it would do it again
[16:05:25 CST(-0600)] <EricDalquist> so it would only do it once per page load?
[16:05:28 CST(-0600)] <drewwills> i was watching the Network tab of chrome dev tool
[16:05:30 CST(-0600)] <drewwills> tools
[16:05:49 CST(-0600)] <prairycat> hey Drew
[16:05:56 CST(-0600)] <drewwills> usually wouldn't even do it then... if I told it to refresh, it seemed to
[16:06:09 CST(-0600)] <drewwills> hi there prairycat
[16:06:28 CST(-0600)] <prairycat> do you know jaffathecake?
[16:06:49 CST(-0600)] <EricDalquist> ok
[16:06:54 CST(-0600)] <drewwills> watching chrome network tab, the call to the action request would be missing... it would just go directly to the URL to which the 302 pointed
[16:07:03 CST(-0600)] <EricDalquist> so I feel like I'm still not seeing the whole picture
[16:07:04 CST(-0600)] <EricDalquist> huh
[16:07:14 CST(-0600)] <EricDalquist> I wonder if that is jquery or chrome
[16:07:22 CST(-0600)] <drewwills> yeah i wondered too
[16:07:22 CST(-0600)] <EricDalquist> does it do the same thing in other browsers?
[16:07:29 CST(-0600)] <drewwills> very good question
[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 
[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