07-06-2007, 08:47 AM
[eluser]sophistry[/eluser]
it was probably a redirect loop that gave a 503 after reaching the resource limit. netsol likely has something (helpful?) in their shared hosting set up that tries to use index.php as a redirect target. just a guess... good that you got it sorted by changing the name of the index.php redirect - but it does seem like an unstable solution. something there is bound to break at some point.
it was probably a redirect loop that gave a 503 after reaching the resource limit. netsol likely has something (helpful?) in their shared hosting set up that tries to use index.php as a redirect target. just a guess... good that you got it sorted by changing the name of the index.php redirect - but it does seem like an unstable solution. something there is bound to break at some point.
