Been trying to resolve this.  I am making a http connection through code; http://www.blah.com
I am supposed to get a response back from "blah.com" with a 302 (redirect response code) and a "location: newpage.com".

Why would I get a different "location" depending on what machine I am running my code from.

running local1 = location: blah.com/blah
running local2 = location: kjsdkfsd.com/huh


I dont know our network setup (and apparently the people I work with dont either).  There are proxy servers setup and whatever else.  If wonder if there is some translation going on at the proxy level that is giving me a different response depending on if I am running from local2.

The application at "blah.com" just does a redirect.

Another way to look at it.  Can network people configure a network such that if a user goes to "http://www.google.com" that they actually get results back from "http://www.yahoo.com".  I assume proxy servers can be configured to do whatever?  Or maybe even firewall servers.

Edit the hosts file to point google.com to yahoo.com's IP?

Or the equivalent in the proxy's DNS resolution.

"Edit the hosts file to point google.com to yahoo.com's IP?

I can't do anything, I was just trying to find out if it is possible.

This is the weirdest thing in the world.  And a little http explanation.

If I do a reqular HTTP request from a client one (which is actually a server):

Request:
GET
http://www.blah1.com

Response:
HTTP/1.1 302 Object moved
Location: http://blah1.com/hello.asp

(that is a good request!!!yea)

If I do a HTTP request from client two (another server)

Request:
GET
http://www.blah1.com

Response:
HTTP/1.1 302 Object moved
Location: http://invalidservermissing.com/hello.asp

(this is a bad request)

So confused.

Is this all happening on an intranet where the clients are on two different subnets?

"Is this all happening on an intranet where the clients are on two different subnets?"

I don't know what that means (not a network person), but that is possible.  Imagine "machine 2" is running from one of those disaster machines where it is separate from everything else, so possibly.

Yeah, it sounds like it could very well be.

Does it act any different hitting the page from the browser of both machines?

And is the web server located on the same network as machine 1?

"And is the web server located on the same network as machine 1?"

Web server is remote (not ours). 

"Does it act any different hitting the page from the browser of both machines?"

Old aix box, don't know if it has a browser application.

I'm thinking the router/proxy/gateway for machine2 is killing the request.

Is invalidservermissing.com machine2's name by any chance?

"I'm thinking the router/proxy/gateway for machine2 is killing the request."

I don't know about killing the request but doing something with the response.

But that doesnt even make sense either.  I hate network people.


"Is invalidservermissing.com machine2's name by any chance?"

invalidservermissing.com is the hostname that the remote server used 5 years ago.  They claim they dont have any reference to that the app on their end just redirects to "blah1.com" which is what I confirmed.

5 years ago? LOL

I don't know much about AIX servers, but maybe it still has that IP/hostname cached somewhere or in something equivalent to a hosts file?

" but maybe it still has that IP/hostname cached somewhere or in something equivalent to a hosts file?"

that is what I was thinking.  I wonder what though and why only on the 302/redirect response.