"RFC 2068 states: Servers should be cautious about depending on URI
lengths above 255 bytes, because some older client or proxy
implementations may not properly support these lengths."
"The spec for URL length does not dictate a minimum or maximum URL
length, but implementation varies by browser. On Windows: Opera
supports ~4050 characters, IE 4.0+ supports exactly 2083 characters,
Netscape 3 -> 4.78 support up to 8192 characters before causing errors
on shut-down, and Netscape 6 supports ~2000 before causing errors on
So even if you set the limit to 2000 characters you still run the risk
of failures due to lesser maximums on browsers that are not explicitly
supported and proxy servers.
I like the idea a lot, I am just concerned about potential failures
that I can't even test for. I don't even think there is a
programmatic solution, and that we would need to rely on good
documentation and possible compile-time warnings.
I would be interested on hearing about some testing results on this.
Specifically, what happens when you exceed the threshold? Also, the
info I provided is a bit old, it would be great to hear if newer
browsers have different limitations.
I use script-tag RPC on Chronoscope too, because in widget deployment
mode, I let people people embed the widget locally, but target an RPC
font-metrics server we host. Luckuly, I know the RPC arguments are
The ugly part doesn't bother me, just as long as it is under the
covers and I don't need to see it.
No, I had not examined that headers. And I hadn't done any special configuration for this responses, just as I hadn't do it for XHR transport. But I've found Script-Tag transport working in IE & Firefox, and totally broken in Opera.
I just have no time now to check for correct headers, sorry.