https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
--- Comment #11 from Ran Rubinstein <[EMAIL PROTECTED]> 2008-07-21 03:41:16
PST ---
(In reply to comment #10)
Will, I'm sorry to drag this on, but I want to understand fully where I'm wrong
in this.
AFAIK, an ascii URL with one chara
https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
--- Comment #10 from Will Rowe <[EMAIL PROTECTED]> 2008-07-17 08:11:57 PST ---
We might have lost sight of the issue here; this issue is not whether or not
it's possible to encode utf-16-le, it's that the URI was not encoded in that
cha
https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
--- Comment #9 from Ran Rubinstein <[EMAIL PROTECTED]> 2008-07-17 01:17:48 PST
---
(In reply to comment #8)
> Of course, whether or not that is a good idea is another question.
>
> So yes, if a server needs to support these kinds of
https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
--- Comment #8 from Julian Reschke <[EMAIL PROTECTED]> 2008-07-16 08:12:02 PST
---
I do(In reply to comment #6)
> If we are to accept UTC-16, let's examine the bytestream of a GET request;
>
> GET
> \0h\0t\0t\0p\0:\0/\0/\0a\0.\0c\0o\0
https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
--- Comment #7 from Ran Rubinstein <[EMAIL PROTECTED]> 2008-07-16 08:09:21 PST
---
(In reply to comment #6)
I was under the impression that only URL parameters that are part of the query
string have to be encoded, and that when decodi
https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
--- Comment #6 from Will Rowe <[EMAIL PROTECTED]> 2008-07-16 07:58:51 PST ---
If we are to accept UTC-16, let's examine the bytestream of a GET request;
GET
\0h\0t\0t\0p\0:\0/\0/\0a\0.\0c\0o\0m\0?\0u\0t\0f\0001\0006\0p\0a\0r\0a\0m\0e\0
https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
Julian Reschke <[EMAIL PROTECTED]> changed:
What|Removed |Added
CC||[EMAIL PROTECT
https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
--- Comment #5 from Julian Reschke <[EMAIL PROTECTED]> 2008-07-16 07:32:26 PST
---
(In reply to comment #3)
> Marking Invalid.
>
> You aren't able to use utf-16 or ucs-2. Period.
>
> The RFC2616 protocol clearly declares the input s
https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
--- Comment #4 from Ran Rubinstein <[EMAIL PROTECTED]> 2008-07-16 06:57:15 PST
---
(In reply to comment #3)
> Marking Invalid.
>
> You aren't able to use utf-16 or ucs-2. Period.
>
> The RFC2616 protocol clearly declares the input s
https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
Will Rowe <[EMAIL PROTECTED]> changed:
What|Removed |Added
Status|NEW |RESOLVED
R
https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
--- Comment #2 from Ran Rubinstein <[EMAIL PROTECTED]> 2008-07-16 06:20:16 PST
---
(In reply to comment #1)
> If you are literally correct below in your observation, the request should
> return 400 invalid, because %D%7 is not valid.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
--- Comment #1 from Will Rowe <[EMAIL PROTECTED]> 2008-07-16 06:14:40 PST ---
If you are literally correct below in your observation, the request should
return 400 invalid, because %D%7 is not valid. 2 hex digits are mandatory.
--
C
12 matches
Mail list logo
