Closed Bug 479615 Opened 15 years ago Closed 15 years ago

findCluster should run only when server is s.m.c

Categories

(Cloud Services :: General, defect)

Product:
Cloud Services
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: anant, Unassigned)

Details

Currently the Weave client uses the API on services.mozilla.com to fetch a cluster name to connect to. This will break users who are setting up their own Weave server.

One possible solution is to use findCluster only if the serverURI is auth.services.mozilla.com. Ideas?
No, it won't break.  If the server returns a 404 for chknode, the client will assume the cluster == server.  So the scenarios are:

1) server is auth.services.mozilla.com

-> chknode will return user's cluster, client will use that.

2) server is a personal one, does not have chknode

-> client will use the personal server as the cluster

3) server is a personal one, does have chknode

-> client will follow chknode as it would for auth.s.m.c

So this is not a bug.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Component: Weave → General
Product: Mozilla Labs → Weave
Version: 0.3 → unspecified
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.