Database says :
mysql> select * from services;
+----+----------+------------------+
| id | service | pattern |
+----+----------+------------------+
| 1 | sync-1.5 | {node}/1.5/{uid} |
+----+----------+------------------+
1 row in set (0.00 sec)
On Jan 30, 2014, at 9:47 PM, Ryan Kelly <[email protected]> wrote:
> On 31/01/2014 6:17 AM, Stefan Arentz wrote:
>> The token server for production is
>> https://token.services.mozilla.com/1.0/sync/1.5 which means ‘give me a token
>> for sync 1.5’. But the endpoint that it returns is
>> https://sync-1-us-east-1.sync.services.mozilla.com/1.1/$UID. Note the 1.5 vs
>> 1.1.
>
> Is it definitely returning that in its response, or is firefox replacing
> the "1.5" with a "1.1" after it is received?
>
> Both have happened at different points in development.
>
>> I am not sure which one is wrong, but i don’t think it is right to ask for a
>> service of a specific version and get back an endpoint for a different
>> (older) version.
>
> We've been a bit fuzzy with this because firefox desktop code was
> hard-coding a 1.1 into the URL. I believe this is pretty much resolved,
> maybe just pending a checkin, so your email is a timely reminder to
> tighten it up :-)
>
> Benson, can you please check the "services" table in prod tokenserver
> database and see what the "pattern" column is for sync? If it still
> contains a "1.1" from our initial testing, I believe it's safe to change
> it back to "1.5" as of now.
>
> (Even if FF is still hard-coding a 1.1 back into the URL, the storage
> servers now have compatibility code to cope with it without help from
> the tokenserver)
>
>
>> (BTW What is the preferred place to file bugs? Github or Bugzilla?)
>
> Bugzilla please. Even if that's not the best place for the specific
> bug, ISTM it's much less likely to get lost on bugzilla than in github.
>
>
> Thanks,
>
> Ryan
>
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
