On Tuesday 07 January 2003 9:17 pm, Susan Aurand wrote:
I know the POST Method the data is sent to STDIN, and GET method the data
is attached to the URL and then submitted. When and why would you want to
use the GET method versus the POST method. Is is because of firewalls? or
what? I would
I have XP Pro and had this problem but I changed my
Server to Apache and it works fine now. (Before
I had VQServer which was using the Sun JRE. which
was interferring).
I dont know if that helps.
Phill.
Paul Kraus [EMAIL PROTECTED] wrote in message
You can generate keep client's status (session) in URI or in cookies.
In the case of URI it's quite simple:
In the script login.cgi you just check if login correct and generate session
string
so link wil look like this
http://www.mydomain.com/cgi-bin/next.cgi?session=567885734957345
Also you save
You can generate keep client's status (session) in URI or in cookies.
In the case of URI it's quite simple:
In the script login.cgi you just check if login correct and generate session
string
so link wil look like this
http://www.mydomain.com/cgi-bin/next.cgi?session=567885734957345
Also you save
On Wednesday, Jan 8, 2003, at 01:21 US/Pacific, Gary Stainburn wrote:
[..]
The only benefits of using GET that I can think of is that you can
emulate a
form by manually keying the data in the URL, and you can even create a
bookmark containing the completed form details. I personally use this
On Wed, 8 Jan 2003 10:02:20 -0800, drieux [EMAIL PROTECTED] wrote:
On Wednesday, Jan 8, 2003, at 01:21 US/Pacific, Gary Stainburn wrote:
[..]
The only benefits of using GET that I can think of is that you can
emulate a
form by manually
Here is a tutorial (written for the CGI::Session
module) with a section on how to do membership style
sites.
http://search.cpan.org/author/SHERZODR/CGI-Session-3.11/Session/CookBook.pm#MEMBERS_AREA
The basic idea is to set a subroutine (included in the
tutorial) at the beginning of each
On Wednesday, Jan 8, 2003, at 12:09 US/Pacific, Susan Aurand wrote:
thanks.
the simplest rule of thumb is
start with GET until you have a good excuse for POST
When you shift towards the 'all POST' approach, then you
also want to be effectively using JavaScripting for the
stuff that needs
On Wednesday, Jan 8, 2003, at 10:19 US/Pacific, [EMAIL PROTECTED]
wrote:
[..]
Good point, this for a *very* long time (and may still be) caused
major headaches for the Mozilla development squad as it render most of
their original implementation of caching completely unusable, as it
related to
