Closed
Bug 477738
Opened 16 years ago
Closed 16 years ago
sm-weave-proxy01 uses old url schema
Categories
(Cloud Services :: General, defect)
Cloud Services
General
Tracking
(Not tracked)
RESOLVED
FIXED
0.3
People
(Reporter: hello, Unassigned)
References
Details
While testing multiple cluster support, I noticed this:
https://sm-weave-proxy01.services.mozilla.com/0.3/user/thunder
yields a 404.
It's because sm-weave-proxy01 is expecting the previous url schema (/weave/0.3/<username>).
Reporter | ||
Comment 1•16 years ago
|
||
Note that when fixing this, we need to fix the services.mozilla.com redirect at the same time, so that current clients that are hitting services.m.c continue to work.
Comment 2•16 years ago
|
||
sm-weave-proxy01 now supports both url formats. That should be the cleanest way to do it.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 3•16 years ago
|
||
I changed it so that sm-proxy01 redirects to the new URL scheme for all incoming requesting (including those for new registrations and password changes). Since the old URL scheme shouldn't be used anymore, anywhere, I also disabled the old URL format on sm-weave-proxy01.
Updated•16 years ago
|
Component: Weave → General
Product: Mozilla Labs → Weave
Updated•16 years ago
|
QA Contact: weave → general
You need to log in
before you can comment on or make changes to this bug.
Description
•