[twitter-dev] Re: Strange 401 errors when having dot in the status update

[guytom]

Thanks.


On Sep 27, 4:56 pm, JDG  wrote:
> From the OAuth spec:
>
> 5.1.  Parameter Encoding
>
> All parameter names and values are escaped using the [RFC3986] (Berners-Lee,
> T., “Uniform Resource Identifiers (URI): Generic Syntax,”
> .)percent-encoding (%xx)
> mechanism. Characters not in the unreserved character
> set ([RFC3986] (Berners-Lee, T., “Uniform Resource Identifiers (URI):
> Generic Syntax,” .)  section 2.3) MUST
> be encoded. Characters in the unreserved character set MUST NOT be encoded.
> Hexadecimal characters in encodings MUST be upper case. Text names and
> values MUST be encoded as UTF-8 octets before percent-encoding them per
> [RFC3629] (Yergeau, F., “UTF-8, a transformation format of Unicode and ISO
> 10646,” .) .
>
>             unreserved = ALPHA, DIGIT, '-', '.', '_', '~'
>
> You can't encode .
>
>
>
>
>
> On Sun, Sep 27, 2009 at 02:59, guytom  wrote:
>
> > Anyone has any idea about this?
>
> > I tracked the request it seems that the server doesn't like the fact
> > that the dot ('.') is also URL encoded. We're using flash AS3 and the
> > URLVariables class automatically encodes it this way, so for example
> > if we send "go to nba.com"
> > It comes out as "status=go%20to%20nba%20%2E%20com" in the POST data
>
> > The encoding of the . is the only one that fails, all other "special"
> > url characters work fine.
>
> > Thanks in advance.
>
> > GT
>
> > On Sep 24, 2:24 pm, guytom  wrote:
> > > That's weird I know...
>
> > > When our application has "." for example "nba.com" in the status
> > > message, the status update API call fails and we get401. other
> > > requests work fine.
>
> > > We use oAuth btw.
>
> > > Any ideas?
>
> > > GT
>
> --
> Internets. Serious business.

[twitter-dev] Re: Strange 401 errors when having dot in the status update

[JDG]

>From the OAuth spec:

5.1.  Parameter Encoding

All parameter names and values are escaped using the [RFC3986] (Berners-Lee,
T., “Uniform Resource Identifiers (URI): Generic Syntax,”
.)percent-encoding (%xx)
mechanism. Characters not in the unreserved character
set ([RFC3986] (Berners-Lee, T., “Uniform Resource Identifiers (URI):
Generic Syntax,” .)  section 2.3) MUST
be encoded. Characters in the unreserved character set MUST NOT be encoded.
Hexadecimal characters in encodings MUST be upper case. Text names and
values MUST be encoded as UTF-8 octets before percent-encoding them per
[RFC3629] (Yergeau, F., “UTF-8, a transformation format of Unicode and ISO
10646,” .) .

unreserved = ALPHA, DIGIT, '-', '.', '_', '~'


You can't encode .

On Sun, Sep 27, 2009 at 02:59, guytom  wrote:

>
> Anyone has any idea about this?
>
> I tracked the request it seems that the server doesn't like the fact
> that the dot ('.') is also URL encoded. We're using flash AS3 and the
> URLVariables class automatically encodes it this way, so for example
> if we send "go to nba.com"
> It comes out as "status=go%20to%20nba%20%2E%20com" in the POST data
>
> The encoding of the . is the only one that fails, all other "special"
> url characters work fine.
>
> Thanks in advance.
>
> GT
>
> On Sep 24, 2:24 pm, guytom  wrote:
> > That's weird I know...
> >
> > When our application has "." for example "nba.com" in the status
> > message, the status update API call fails and we get401. other
> > requests work fine.
> >
> > We use oAuth btw.
> >
> > Any ideas?
> >
> > GT
>



-- 
Internets. Serious business.

[twitter-dev] Re: Strange 401 errors when having dot in the status update

[guytom]

Anyone has any idea about this?

I tracked the request it seems that the server doesn't like the fact
that the dot ('.') is also URL encoded. We're using flash AS3 and the
URLVariables class automatically encodes it this way, so for example
if we send "go to nba.com"
It comes out as "status=go%20to%20nba%20%2E%20com" in the POST data

The encoding of the . is the only one that fails, all other "special"
url characters work fine.

Thanks in advance.

GT

On Sep 24, 2:24 pm, guytom  wrote:
> That's weird I know...
>
> When our application has "." for example "nba.com" in the status
> message, the status update API call fails and we get401. other
> requests work fine.
>
> We use oAuth btw.
>
> Any ideas?
>
> GT