www-trunk.stage.m.c is going through the netscaler

RESOLVED WORKSFORME

Status

mozilla.org Graveyard
Server Operations
RESOLVED WORKSFORME
10 years ago
3 years ago

People

(Reporter: clouserw, Unassigned)

Tracking

Details

(Reporter)

Description

10 years ago
I don't know when this started but this is a development site and shouldn't be going through the netscaler - we need to see changes on it right away.

Comment 1

10 years ago
I'm fairly certain it's always been this way.
(Reporter)

Comment 2

10 years ago
I think I would have noticed it before now but you could be right.  It doesn't make sense though since authstage.m.c doesn't go through the netscaler  and stuff hits trunk before authstage.

(Also, I no longer see netscaler headers on www-trunk.s.m.c.  Perhaps someone just fixed this?)

Comment 3

10 years ago
No, IP hasn't changed.

Stage is supposed to nearly mirror production so in that respect it should live behind the Netscaler.  

btw. authstage also goes through the Netscaler.  If the IP address starts with 63.245.209 it's the Netscaler.

Is there any action on this bug?
(Reporter)

Comment 4

10 years ago
I don't see netscaler headers on www-trunk or authstage now so I'm willing to call this bug fixed (or invalid or whatever, but they were on www-trunk earlier).
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED

Comment 5

10 years ago
Just verifying that it has always been behind the netscaler.  If you notice objects coming from cache I can think of two solutions:

* send no-cache headers from the stage vhost
* add a "dev" config variable to the mozilla.com code that will send no-cache headers
Resolution: FIXED → WORKSFORME
(Reporter)

Comment 6

10 years ago
Neither www-trunk or authstage has ns-cache headers right now.

I'm not complaining because I don't think they should, I'm just mentioning it because I guess you both think they are there?
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.