Session maintenance

[Michael Satterwhite]

I'm trying to get a better feel for exactly how sessions work.

At the beginning of a web page, I do either a session_start() or a
session_registe r(...). When the user goes to the next page, I know the page
needs to get the SSID. I know I can send it as a cookie, hidden field, etc,
but what other ways are available to send it? For example, I know that
session_registe ring variables at the top of the second page works.

If the user visits any pure html pages (extension html), how can I get the
session back when they come back to my php pages. Without php on the page,
how can I propagate the SSID?

thanks in advance
---Michael

[R. Rajesh Jeba Anbiah]

Michael Satterwhite wrote:

I'm trying to get a better feel for exactly how sessions work.

At the beginning of a web page, I do either a session_start() or a
session_registe r(...). When the user goes to the next page, I know the page needs to get the SSID. I know I can send it as a cookie, hidden field, etc, but what other ways are available to send it? For example, I know that session_registe ring variables at the top of the second page works.

If the user visits any pure html pages (extension html), how can I get the session back when they come back to my php pages. Without php on the page, how can I propagate the SSID?

IMHO, there is no way to carry the session id in pure html pages.
Probably you may need to force the html pages to be parsed by PHP (by
settings in Apache). May also want to try trans sid setting.
session_registe r() is obsolete. Please refer manual
<http://www.php.net/session>

--
<?php echo 'Just another PHP saint'; ?>
Email: rrjanbiah-at-Y!com Blog: http://rajeshanbiah.blogspot.com/

[Alvaro G. Vicario]

*** Michael Satterwhite escribió/wrote (Sun, 13 Feb 2005 15:32:11 GMT):

If the user visits any pure html pages (extension html), how can I get the
session back when they come back to my php pages.

Just let PHP take care of it with the default solution: cookies.
--
-+ Álvaro G. Vicario - Burgos, Spain
+- http://www.demogracia.com (la web de humor barnizada para la intemperie)
++ Manda tus dudas al grupo, no a mi buzón
-+ Send your questions to the group, not to my mailbox
--

[Matthias Esken]

Michael Satterwhite wrote:

At the beginning of a web page, I do either a session_start() or a
session_registe r(...).

You don't want to use session_registe r(). Use the $_SESSION array.

Regards,
Matthias

[Derek Fountain]

> At the beginning of a web page, I do either a session_start() or a

session_registe r(...).
You do a session_start() . session_registe r() is obsolete. :)
When the user goes to the next page, I know the
page needs to get the SSID. I know I can send it as a cookie, hidden
field, etc, but what other ways are available to send it? For example, I
know that session_registe ring variables at the top of the second page
works.
The session handling in PHP does this for you automatically. Just call
session_start() at the very top of each page and PHP will pick up the
session id and restore the $_SESSION array for you. For many (most?)
purposes you don't *need* to know what the session ID is or how it is sent.
(It normally goes via a cookie and you can find the value with
session_id().)
If the user visits any pure html pages (extension html), how can I get the
session back when they come back to my php pages. Without php on the page,
how can I propagate the SSID?

Any page that needs the session ID just calls session_start() at the top.
That makes $_SESSION available. If you have any pages (PHP or HTML) that
don't need the session just ignore it by not calling session_start() . The
session ID is propagated automatically by the browser, which sends it with
each page request. If the server doesn't use (or even look at) that cookie,
that won't stop the browser sending it with the next page request.

--
The email address used to post is a spam pit. Contact me at
http://www.derekfountain.org : <a
href="http://www.derekfounta in.org/">Derek Fountain</a>

[Jerry Sievers]

Michael Satterwhite <sa************ *****@weblore.c om> writes:

I'm trying to get a better feel for exactly how sessions work.

At the beginning of a web page, I do either a session_start() or a
session_registe r(...). When the user goes to the next page, I know the page
needs to get the SSID. I know I can send it as a cookie, hidden field, etc,
but what other ways are available to send it? For example, I know that
session_registe ring variables at the top of the second page works.

If the user visits any pure html pages (extension html), how can I get the
session back when they come back to my php pages. Without php on the page,
how can I propagate the SSID?
The cookie SID storage method is going to result in the client sending
the SID cookie with each request to a qualified directory regardless
of the target page being a static file or script.
thanks in advance
---Michael

--
-------------------------------------------------------------------------------
Jerry Sievers 305 854-3001 (home) WWW ECommerce Consultant
305 321-1144 (mobile http://www.JerrySievers.com/

[Michael Satterwhite]

Jerry Sievers wrote:

Michael Satterwhite <sa************ *****@weblore.c om> writes:

I'm trying to get a better feel for exactly how sessions work.

At the beginning of a web page, I do either a session_start() or a
session_registe r(...). When the user goes to the next page, I know the
page needs to get the SSID. I know I can send it as a cookie, hidden
field, etc, but what other ways are available to send it? For example, I
know that session_registe ring variables at the top of the second page
works.

If the user visits any pure html pages (extension html), how can I get
the session back when they come back to my php pages. Without php on the
page, how can I propagate the SSID?

The cookie SID storage method is going to result in the client sending
the SID cookie with each request to a qualified directory regardless
of the target page being a static file or script.

Exactly what are you referring to here? I'm feeling very ignorant at this
point.

thanks much
---Michael

[Jerry Sievers]

Michael Satterwhite <sa************ *****@weblore.c om> writes:

Jerry Sievers wrote:

Michael Satterwhite <sa************ *****@weblore.c om> writes:
The cookie SID storage method is going to result in the client sending
the SID cookie with each request to a qualified directory regardless
of the target page being a static file or script.
Exactly what are you referring to here? I'm feeling very ignorant at this
point.

I don't know where to begin. You have read all the PHP docs that
pertain to sessions, right?

Among possible others, the session ID can be sent to the server by a
query parameter in the URL or a cookie.

You should dig through the bunches of session related PHP config
settings to get a better idea what's possible.

I prefer to force cookies and disable transparent SID;

php_flag session.auto_st art on
php_flag session.use_onl y_cookies on
php_flag session.use_tra ns_sid off

I don't know is this helps or not.

Good luck. Sessions are hairy but very useful.

thanks much
---Michael

--
-------------------------------------------------------------------------------
Jerry Sievers 305 854-3001 (home) WWW ECommerce Consultant
305 321-1144 (mobile http://www.JerrySievers.com/

--
-------------------------------------------------------------------------------
Jerry Sievers 305 854-3001 (home) WWW ECommerce Consultant
305 321-1144 (mobile http://www.JerrySievers.com/

[Michael Satterwhite]

Jerry Sievers wrote:

Michael Satterwhite <sa************ *****@weblore.c om> writes:

Jerry Sievers wrote:

> Michael Satterwhite <sa************ *****@weblore.c om> writes:
>
>
> The cookie SID storage method is going to result in the client sending
> the SID cookie with each request to a qualified directory regardless
> of the target page being a static file or script.

Exactly what are you referring to here? I'm feeling very ignorant at this
point.

I don't know where to begin. You have read all the PHP docs that
pertain to sessions, right?

Absolutely ... and have been using sessions. My question here is specific
to: "What are you referring to by the "cookie SID storage method"?

I know that I can send the SID in many ways, but it is my understanding that
*I* have to send it (post, cookie, whatever). The post I'm replying to is
(I believe) implying that once I send it the server is going to continue to
send it - even to downstream pages where I haven't sent it. I would love
for that to be true (and, in my ignorance, I allow for the fact that it may
be!) but I haven't seen - or have missed - anything in the documentation
that says that. If there *IS* a storage method that propagates the SID to
downstream pages, I really want to understand it so that I can use it.

[Jerry Sievers]

Michael Satterwhite <sa************ *****@weblore.c om> writes:

Jerry Sievers wrote:
Absolutely ... and have been using sessions. My question here is specific
to: "What are you referring to by the "cookie SID storage method"?

I know that I can send the SID in many ways, but it is my understanding that
*I* have to send it (post, cookie, whatever). The post I'm replying to is
(I believe) implying that once I send it the server is going to continue to
send it - even to downstream pages where I haven't sent it. I would love
for that to be true (and, in my ignorance, I allow for the fact that it may
be!) but I haven't seen - or have missed - anything in the documentation
that says that. If there *IS* a storage method that propagates the SID to
downstream pages, I really want to understand it so that I can use it.
I have NOT done any actual R&D to verify this but it's likely that the
server send the set cookie header only the first time on session start
if it doesn't get a SID.

From that point, the client sends the cookie to identify the session.

And it should send this cookie to any URL that the cookie is intended
for which I believe on sessions (the default) is the entire site.

HTH

--
-------------------------------------------------------------------------------
Jerry Sievers 305 854-3001 (home) WWW ECommerce Consultant
305 321-1144 (mobile http://www.JerrySievers.com/