Some links redirecting to Domain.com

Jochen Arndt

I'm posting this here because the information may help to track down the issue. [EDIT] If this is server dependant: I have actually connections the web02 and web03 servers. [/EDIT] I have used wget to check the server responses:

data:~ # wget -vS --save-headers --no-cache http://www.codeproject.com/
--2015-01-09 13:30:36-- http://www.codeproject.com/
Resolving www.codeproject.com... 65.39.148.34
Connecting to www.codeproject.com|65.39.148.34|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html; charset=utf-8
Set-Cookie: SessionGUID=2b2547f6-9f1b-406a-9b54-195a3aef05ae; path=/
Set-Cookie: SessionGUID=2b2547f6-9f1b-406a-9b54-195a3aef05ae; path=/
Set-Cookie: vk=7b0294a3-77e2-49b6-85c1-e1430eb7cd47; domain=.codeproject.com; expires=Sat, 09-Jan-2016 05:00:00 GMT; path=/; HttpOnly
Date: Fri, 09 Jan 2015 12:30:36 GMT
Connection: keep-alive
Content-Length: 73999
Length: 73999 (72K) [text/html]

The above is the expected behaviour. This happens when redirecting occurs:

data:~ # wget -vS --save-headers --no-cache http://www.codeproject.com/
--2015-01-09 13:30:59-- http://www.codeproject.com/
Resolving www.codeproject.com... 65.39.148.34
Connecting to www.codeproject.com|65.39.148.34|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 301 Moved Permanently
Cache-Control: private
Content-Type: text/html; charset=utf-8
Location: http://www.domain.com//
Set-Cookie: SessionGUID=5eb3d887-659d-4370-9056-12218ff949b7; path=/
Set-Cookie: SessionGUID=5eb3d887-659d-4370-9056-12218ff949b7; path=/
Set-Cookie: vk=cdc9416e-16cc-4a38-91eb-dfc3df079f9e; domain=.domain.com/; expires=Sat, 09-Jan-2016 05:00:00 GMT; path=/; HttpOnly
Date: Fri, 09 Jan 2015 12:30:58 GMT
Connection: keep-alive
Content-Length: 140
Cookie coming from www.codeproject.com attempted to set domain to domain.com/
Location: http://www.domain.com// [following]
--2015-01-09 13:31:00-- http://www.domain.com//
Resolving www.domain.com... 65.254.244.180
Connecting to www.domain.com|65.254.244.180|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Date: Fri, 09 Jan 2015 12:31:00 GMT
Content-Type: text/html; charset=ISO-8859-1
Content-Length: 18476
Connection: keep-alive
Server: Apache
X-Frame-Options: SAMEORIGIN
Pragma: no-cache
Cache-control: no-cache
Expires: Fri, 09 Jan 2015 12:31:00 GMT
Set-Cookie: SESSION_ID=bcc823

V 0

Same issue here ...

V.
(MQOTD rules and previous solutions)

Keith Barrow

I tried using the IP directly - got the domain.com page again. Don't know if this will help the hamsters....

Slacker007 wrote:

[Dalek] Dave would make a fine American.[^]

Lost User

We had in our company (Switzerland) just before an internet interruption for about 10 minutes. Now INet is back an problems on CP disapeared.....

Paw Jershauge

Same here :doh: :doh: :doh: :doh: :doh:

With great code, comes great complexity, so keep it simple stupid...:-\ :-\

CHill60

Still getting it in UK :( Phone ok-ish. Refresh not working on laptop. Getting withdrawal symptoms!

Lost User

Seems OK in Woking now. :-D

CHill60

Yay! Unfortunately I'm out now :(

_AK_

This issue is still there so many forums.

.AK.

Corporal Agarn

IE is okay, FireFox goes to domain.com

Matthew Dennis

A poorly timed network error triggered an very old, previously undiscovered bug. Chris has rebooted the servers and is working on the bug fix. Everything should be ok, but you may need to refresh your browser cache. Thank you for your patience and great information. It made tracking down the issue so much easier.

Lost User

Thank you very much for your feedback. But sorry, it is hard to believe that a bug on your side caused all the redirections :~ Bruno

Rajesh waran

Yes you're right i have that too. i can't signed in here with my account yesterday.But now solved:thumbsup:

~R@JEES#

Rajesh waran

:thumbsup:

~R@JEES#

Chris Maunder

Still?

cheers Chris Maunder

Corporal Agarn

yep. Monday 6:37am est

Lost User

Matthew Dennis wrote:

Everything should be ok, but you may need to refresh your browser cache.

Are you sure its not a DNS issue?

Matthew Dennis

Very sure. It was the result of some extremely embarrassing code.