You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: avarab[at]gmail.com [Submitted to the original trac issue database at 5.51pm, Sunday, 13th September 2009]
Rails will throw a 500 error when you give it a ISO 8859-1 username. See [http://josm.openstreetmap.de/ticket/3483 the JOSM ticket] for a network sniff.
The text was updated successfully, but these errors were encountered:
Author: TomH [Added to the original trac issue at 7.28pm, Sunday, 13th September 2009]
I think the obvious question here is, what do you think it should do? I'm not even sure the HTTP specification provides any way to know what the encoding of the authentication header is does it?
Author: avarab[at]gmail.com [Added to the original trac issue at 7.45pm, Sunday, 13th September 2009]
Replying to [comment:1 TomH]:
I think the obvious question here is, what do you think it should do? I'm not even sure the HTTP specification provides any way to know what the encoding of the authentication header is does it?
Maybe give an error when the user provides an invalid UTF-8 sequence instead of sending it at the database which will result in an internal error?
I don't know. I just file bugs for things which are internal errors by reflex.
Reporter: avarab[at]gmail.com
[Submitted to the original trac issue database at 5.51pm, Sunday, 13th September 2009]
Rails will throw a 500 error when you give it a ISO 8859-1 username. See [http://josm.openstreetmap.de/ticket/3483 the JOSM ticket] for a network sniff.
The text was updated successfully, but these errors were encountered: