868484 - Android Sync doesn't support configuring custom server with path prefix

Status: RESOLVED INVALID

(Firefox for Android Graveyard :: Android Sync, defect)

Description

[alex]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0
Build ID: 20130417085609

Steps to reproduce:

- use a own sync server (which works great with desktop firefox), installed on http://host/weave/
- setup it in firefox for android (works)
- try to sync
- firefox for android tries to get the the collectionsurl


Actual results:

firefox uses the hostname, but not the path component of the sync-url:

x.x.x.x MYSYNCSERVER - [03/May/2013:19:01:09 +0200] "GET /1.1/USERNAME/info/collections HTTP/1.1" 404 1150 "-" "Firefox AndroidSync 1.20.0.1.0 (Firefox)"


Expected results:

firefox should use the whole sync-url as prefix, like this:

x.x.x.x MYSYNCSERVER - [03/May/2013:19:01:09 +0200] "GET /weave/1.1/USERNAME/info/collections HTTP/1.1" 404 1150 "-" "Firefox AndroidSync 1.20.0.1.0 (Firefox)"

Comment 1

[Richard Newman [:rnewman]]

Path prefixes are not supported for Sync servers. This shouldn't work on desktop, either; that it does is an accident.

Comment 2

[alex]

seems only to happen when configuring with sync-key and without mozilla-server using the 3x4-digit sync-code.

Comment 3

[alex]

(In reply to Richard Newman [:rnewman] from comment #1)
> Path prefixes are not supported for Sync servers. This shouldn't work on
> desktop, either; that it does is an accident.

Maybe /weave/ is a special prefix there? Anyway, it IS the default for the django-sync-server and it works with desktop clients. 
I do not see any reason why this should not work, as the sync-server field takes an url not a servername.

Comment 4

[Richard Newman [:rnewman]]

Please remember to refresh the page before commenting, or you'll blow away bug changes.

Comment 5

[Richard Newman [:rnewman]]

(In reply to Alexander Schier from comment #3)

> Anyway, it IS the default for the
> django-sync-server and it works with desktop clients. 

You should file a bug against django-sync-server. This isn't a supported configuration (on Android *or* desktop). If it works by accident (as apparently it does for some setup flows), then good for you, but it's not QAed or maintained.

Comment 6

[alex]

(In reply to Richard Newman [:rnewman] from comment #4)
> Please remember to refresh the page before commenting, or you'll blow away
> bug changes.

yeah, sorry.

(In reply to Richard Newman [:rnewman] from comment #5)
> (In reply to Alexander Schier from comment #3)
> 
> > Anyway, it IS the default for the
> > django-sync-server and it works with desktop clients. 
> 
> You should file a bug against django-sync-server. This isn't a supported
> configuration (on Android *or* desktop). If it works by accident (as
> apparently it does for some setup flows), then good for you, but it's not
> QAed or maintained.

Okay. Seems not to be a django-sync-server bug anyway, because its just a django-package which can be deployed to any url, and /weave was a prefix chosen by me. I migrated from one of the earliest versions of weave implemented in php, which had this path ;).