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: dair[at]refnum.com [Submitted to the original trac issue database at 11.55am, Monday, 16th July 2007]
[http://www.openstreetmap.org/traces/mine Uploading] a GPS trace with Safari fails with:
Application error
Change this error message for exceptions thrown outside of an action
(like in Dispatcher setups or broken Ruby code) in public/500.html
The error comes back immediately, so I suspect the track just isn't being attached for some reason (!FireFox works as expected, with a short delay from hitting submit to getting the result back).
The text was updated successfully, but these errors were encountered:
Author: tom[at]compton.nu [Added to the original trac issue at 11.47pm, Tuesday, 21st August 2007]
sorry to be a pain, but I didn't see your previous response before the logs expired - could you try it again and let me have the details. Trac is sending email now so I will actually see your response straight away this time.
Author: tom[at]compton.nu [Added to the original trac issue at 11.19pm, Wednesday, 22nd August 2007]
This is being triggered by a bug/misfeature in Safari whereby it sometimes doesn't sent a Content-Type header for an uploaded file. As a result rails winds up trying to treat it as an ordinary string parameter instead of an uploaded file - more details at:
Reporter: dair[at]refnum.com
[Submitted to the original trac issue database at 11.55am, Monday, 16th July 2007]
[http://www.openstreetmap.org/traces/mine Uploading] a GPS trace with Safari fails with:
The error comes back immediately, so I suspect the track just isn't being attached for some reason (!FireFox works as expected, with a short delay from hitting submit to getting the result back).
The text was updated successfully, but these errors were encountered: