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: ivansanchez[at]escomposlinux.org [Submitted to the original trac issue database at 2.46pm, Sunday, 8th February 2009]
I'm using the Rails port rev. 13597 (2008-02-08) in a test environment. I can hang up the rails server by uploading a well-formed but empty changeser.
How to reproduce: upload an empty osmChange file to a malformed URL. The URL has to be one of a changeset upload, but with a null changeset. Note the '//': POST http://(user):(passwd)@localhost:3000/api/0.6/changeset//upload
Reporter: ivansanchez[at]escomposlinux.org
[Submitted to the original trac issue database at 2.46pm, Sunday, 8th February 2009]
I'm using the Rails port rev. 13597 (2008-02-08) in a test environment. I can hang up the rails server by uploading a well-formed but empty changeser.
How to reproduce: upload an empty osmChange file to a malformed URL. The URL has to be one of a changeset upload, but with a null changeset. Note the '//':
POST http://(user):(passwd)@localhost:3000/api/0.6/changeset//upload
Any of the following examples will do:
Interestingly enough, this won't trigger the bug:
The ruby process seems to enter an infinite loop and waste 100% CPU. I consider this bug to be a potential DoS attack on the API servers.
The text was updated successfully, but these errors were encountered: