Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

We have different development severs and a production server. Testing is done in the development servers. As a QA engineer, I'm switching between these servers quite often throughout the day.

In Chrome, sometimes I need to reload a page a few times to get it to pull from the newly switched server.

In Firefox, sometimes I need to quit the browser in order to get it to pull from the newly switched server.

(We have small tags that indicate which server you are pulling from, which is how I know in-browser.)

Why does that happen? I'd love to know how that happens (maybe what it's called?) and what the best way to deal with it is. (I know that Firefox has an extension for domain switching; is that the best solution?)

share|improve this question
    
This happens because Firefox keeps the socket open (you can see this with netstat). Once the socket is closed it will connect to the new one. I don't know of a way to force firefox to close the socket except by quitting. –  bahamat Mar 9 '11 at 23:56
    
I think this is a valid answer. You should move this to that section to get some reputation! –  Jeremy Detrempe Mar 10 '11 at 19:18
    
@Jeremy I'll take it ;-) –  bahamat Mar 10 '11 at 20:03
    
How do you switch between these servers? Do they have different domain names, IP addresses, ...? –  Arjan Mar 10 '11 at 20:14
    
@Arjan They have different IP addresses, but the same domain name. So I'll change my hosts file to reflect the new IP address for the same domain. Does that make sense? We're not sure that that's the best way to switch environments, but that's what we have implemented atm. If you have a better way of doing it, please share! I'd love some feedback. –  Jeremy Detrempe Mar 10 '11 at 23:37

1 Answer 1

up vote 2 down vote accepted

This happens because Firefox keeps the socket open (you can see this with netstat). Once the socket is closed it will connect to the new one. I don't know of a way to force firefox to close the socket except by quitting.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.