<!-- snip -->
It sounds like your code is hokey, since IE is more stringent then
other browsers, the code looks to be at fault.
What browsers did you test this with before taking it to the client?
Firewalls shouldn't be any type of issue at all in this case, unless
your browser is trying to redirect to another port, in which case,
that should be something that the firewall won't affect internally
anyways.
So all roads point back to code failure.
Wolf
The code has been tested on Win2k, XP, Vista, Linux and OSX - IE5.x,
IE6.x, IE7, Netscape 9, Firefox 2, Firefox 5 beta 5, and Safari. Works
on a variety of connections and locations outside of the clients office
- does not work inside the clients office.
Still, your code should be portable, so unless you are kicking it around
different servers from a localhost to an outside host, your going to be
dealing with hokey code...
In other words, if you brought your demo in on your laptop, powered it
up and got a network connection, all your stuff locally stored on the
machine ran and then going to the server didn't, then something in your
code is stopping the process, and without looking at your server logs,
then you have to go back and examine your code for the authorization
pieces to make sure that your failures are putting SOMETHING to the
screen when it dies.
But if that is the case, it's still coding failure and shouldn't be
something that is noticeable.
Based off your description of the issue, it's code, plain and simple.
No network issues should be an issue unless you are trying to bounce
through different ports and different locations. And if that is the
case and the client would have to open their firewall just to run your
application, they'll look elsewhere.
Grab your log files for that timeframe and start digging through them.
Your best bet in nipping it in the bud before failing again in front of
them is there.
Wolf
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
