Posted by Rik on 02/06/07 18:28

hman <flhman43@hotmail.com> wrote:

Please don't toppost, and for that matter: do not mulitpost. Crosspost if
you really have to.

> Harry Hambrick
> "Rik" <luiheidsgoeroe@hotmail.com> wrote in message
> news:op.tnb8s3erqnv3q9@misant.kabel.utwente.nl...
>> hman <flhman43@hotmail.com> wrote:
>>> If you use a URL of http://statuspage.cosite.com - They get the blank
>>> page
>>> after the login page.
>>
>> So, what's the code after the login? We cannot guess this.
>>
>> Also, check what the servers sends as headers (use Fiddler for MSIE or
>> LiveHTTPHeaders for FireFox to check those).
>
> After the login page, it just loads the page that sets up the frames
> which
> loads a php page into the bottom frame.

And what would be in that page? That is the code that fails, and you give
us no clue what it actually does, so we cannot say anything usefull about
it.

Any way to flag something that the script was indeed run, just the output
isn't received?

> What should I look for in the header? I will find Fiddler to look at it
> but
> not sure what I should your wanting me to look for.

Do you really get a 200 OK, or something else? I.e: did you indeed get an
empty page served, or is there an error which prevents sending at all.

Also, what if you enable display_errors && error_reporting(E_ALL)?

>>> My cookies are set as:
>>>
>>> setcookie("UserKey", $UK,$expiretime);
>>>
>>> setcookie("PHPSESSID",$_COOKIE["PHPSESSID"],$expiretime);
>>>
>>> $expiretime is a variable containing the expiration time of the cookie
>>
>> Cookies are domain specific, but should work if you indeed use
>> http://statuspage.cosite.com as address of the server that sets the
>> cookies.
>
> As far as the cookies go, do I need to specify the domain and path in the
> cookies for them to work with both the domain and the machine name?

Normally, no, server and path default to the current. Users connecting by
one address should have no trouble continuing using that address, and the
cookies it sets. Switching would make your cookies invalid for that
ip/name/server, as they've been set for the other. The browser just won't
send them. You can _try_ to set a cookie for another domain/ip/machine
name, but this would cookie would be declined by the standard settings of
most modern browsers.

--
Rik Wasmus

[Back to original message]