Switching to POST. Thanks.
On Mar 7, 2007, at 10:01 AM, Patrick Berry wrote:
The HTTP protocol does not place any a priori limit on the length of
a URI. Servers MUST be able to handle the URI of any resource they
serve, and SHOULD be able to handle URIs of unbounded length if
they
provide GET-based forms that could generate such URIs. A server
SHOULD return 414 (Request-URI Too Long) status if a URI is longer
than the server can handle (see section 10.4.15).
My bad...still...that's a lot of data.
On 3/7/07, Patrick Berry <[EMAIL PROTECTED]> wrote:
Is it just me or is that an insane amount of data to send via GET?
Mongrel is pretty strict about how clients use HTTP, so check your
mongrel logs.
On 3/7/07, Joe Lester <[EMAIL PROTECTED]> wrote:
My rails web app (rails 1.2.1) uploads an image from a Java applet by
encoding it into the URL. This works fine when I'm using Webrick. I'm
trying out Mongrel today, and I'm getting an error in Safari that
says "lost network connection" (NSURLErrorDomain:-1005). I get
something similar in Firefox. Is there a way to make Mongrel accept a
really long URL like this?
Thanks. Joe.
I'm encoding the 512 x 512 jpeg image as Base64. The long URL is
something like...
http://localhost/account/upload?image=%2F9j%2F4AAQSkZJRgABAQAAAQABAAD%
2F2wBDAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB
AQ
EBAQEBAQEBAQEBAQEBAQH%
2F2wBDAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB
AQ
EBAQEBAQEBAQEBAQEBAQH%2FwAARCAIAAgADASIAAhEBAxEB%
2F8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL%
2F8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0
fA
kM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1d
nd
4eXqDhIWGh4iJipKTlJWW......... [much more]
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users
