Can we fix our Trac that doesn't lose new ticket text

Dan Doel dan.doel at
Fri Apr 24 17:17:45 UTC 2015

At a guess, I recently had some websites start refreshing more than I
thought they used to when using the back/forward buttons. From what I
gather, this is due to the websites specifying no-cache or something
similar in their HTTP (?) headers. I think reloading the page throws away
entered text, while going back/forward to a stored page does not.

Perhaps something the ghc trac is using is setting this? Or it could be
something outside trac entirely?

Also wouldn't surprise me if Chrome behaves differently with such a setting
than Firefox.

Not sure if that helps.

On Fri, Apr 24, 2015 at 9:54 AM, Edward Z. Yang <ezyang at> wrote:

> Steps to reproduce:
> 1. Click "New Ticket"
> 2. Type some text into the box
> 3. Press "Back" in your browser
> 4. Press "Forward" in your browser
> If you try this with an official Trac this doesn't happen, so either
> this was fixed in a new version, or we have a plugin installed which
> is causing this to happen.
> Current version of Trac is 1.0.5, we're currently running 1.0.1
> Thanks,
> Edward
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ghc-devs mailing list