I can't pull up an example right now unfortunately since it's only occasional. I think the URLs are the ones with
_ew_ in the path.
And then if the response gets cached, then subsequent page loads still don't work either.
[#7028] was for the same issue, so see that for additional details. That ticket just resulted in a workaround, but its not great (especially if it gets cached). This ticket is for a real fix.
Log in to post a comment.
tl;dr I've fixed one issue in EasyWidgets and upgraded Allura's version of it. Not sure if it fixes root cause
I'm not sure why the content type is missing (and not detected) in the first place, but I have found a bug in EasyWidgets where the headers from one request were essentially being saved and re-used again for subsequent requests. This is fixed in https://bitbucket.org/rick446/easywidgets/commits/e7cb2dc70fe976e15d3bc2f6987ac9e9feb280c9
You can see for example:
Upgrading EasyWidgets should fix that particular bug. Not entirely sure if it fixes the original issue, since I dont' know why the type isn't picked up the first time, sometimes. So I've gone ahead and done that, but leaving this ticket open to find out if any issues remain.
If/when we finally fix this, we should also remove the
<h2 class="hidden">section in
Allura/allura/templates/jinja_master/master.html. It shows up in search engines sometimes :(
I've removed the hidden CSS mimetime notice and cache clearing recommendation. We want to know if this happens any more. If it does, we can reopen a ticket.