Last week a thread went by that was a discussion on the merits of using the
REMOTE_ADDR as an element of several parts to "secure" (other unique items
were to be the USER_AGENT, etc.). I'd like to incorporate the lists
collective wisdom.
What was the list's conclusion on this matter? It
I'm trying to write a cookie that is properly read by two hosts of the same
domain.
The hosts:
https://secure.domain.com
http://www.domain.com
With PHP 4.1.1 for Linux on Apache (as module) I've written
setcookie("session",$sesscode, "/", "domain.com", "0");
and
setcookie("session"
I must've set something somewhere so that my session writes don't commit
anything. My reads work if I dummy-up some data. My system used to work.
I haven't changed user or group on Apache, user rights seem ok, Mysql is ok,
Mysql rights are ok.
My env: PHP 4.1.1, RH Linux 7.1, Apache 1.3.
I am converting my sessions code to use the new $_SESSION method for
addressing session variables. My session_set_save_handler is written for
MySQL and was working until I started changing external routines to not use
$HTTP_SESSION_VARS and session_register.
My debugging shows that the $_
Maybe I'm having a brain fart, please set me straight:
I want to use session_id($myval) to use a roll-my-own MD5 session id (SID).
I don't obviously want to assign the session_id() if the session is already
established.
Given that session_id() must come before session_start() how do yo
check into libcurl and the php/curl integration. You are certainly able to
process the response headers in curl.
> Hello,
>
> Alexandre Ferreira Novello wrote:
>>
>> Hello guys,
>>
>> I asked that before, but I will explain my problem with more details.
>>
>> How can I retrieve the
Problem: hosts "http://www."; and "https://secure."; of the same domain need
to work with the same browser session_id. This is a
login/authenticate/redirect scenario. In this case the session data store
is a common MySQL database, so the issues of /tmp sharing, NFS, etc. are set
aside. My
7 matches
Mail list logo