[wpmu-trac] Re: [WordPress MU Trac] #189: Infinite redirect if using a port number

[WordPress MU Trac]

#189: Infinite redirect if using a port number
------------------------+---------------------------------------------------
 Reporter:  dwille      |        Owner:  somebody
     Type:  defect      |       Status:  reopened
 Priority:  normal      |    Milestone:  WPMU 1.0
Component:  component1  |      Version:  1.0     
 Severity:  blocker     |   Resolution:          
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by magnayn):

  * status:  closed => reopened
  * resolution:  wontfix =>

Comment:

 Oh dear.

 I have just been caught out by this bug. We were trying to use mu for
 internal (non public facing) blogs in a corporate environment, as a fair
 number of companies are doing this these days, rather than having an admin
 create discrete wordpress installs per user.

 Not only is it entirely common policy to have internal servers on
 alternate ports (8080, 88, 8000, etc); it's /particularly/ nasty to have
 it fail in a 'die in an infinite loop' rather than 'detect, report error'.
 At the very least that needs to be fixed, and the underlying problem ought
 to be fixed too. Wordpress is perfectly happy on alternate ports, why not
 MU.

-- 
Ticket URL: <http://trac.mu.wordpress.org/ticket/189#comment:2>
WordPress MU Trac <http://mu.wordpress.org/>
WordPress Multiuser