Closed wrought closed 8 years ago
In my local environment, this error went away after a few minutes. I was able to browse to /~user
without this error. No explanation so far.
This happens when the server writes to the response twice.
Fixed by 5cb54cf16124de515c8e4a686dc2b0d73f4f9102
I've seen this several times -- both in trying to browse to
/~user
in my local development environent, and also when we have an issue with a user editing their account information #56 What does it mean?