Steffers wrote:
>
> hello,
> first let me apologise for jst jumping straight into asking
> questions on the mailing list, but this is really puzzling me. First
> some background.
>
> I have been using perl for the past 3 years. I think (note
> +think+) that I understand perl quit
Drew wrote:
> Steffers wrote:
> > my $header_ID=$r->header_in('sessionID');
> If you're trying to get at the cookie, this is not the way. Either use
> Apache::Cookie or CGI.pm to get the cookie contents.
>
okay. I have changd the line to the usual
my $header_ID=cookie(-name=>'sessionID
Steffers wrote:
>
> Drew wrote:
> > Steffers wrote:
> > > my $header_ID=$r->header_in('sessionID');
> > If you're trying to get at the cookie, this is not the way. Either use
> > Apache::Cookie or CGI.pm to get the cookie contents.
> >
>
> okay. I have changd the line to the usual
>
> m
Drew wrote:
> Going by your previous example, you should use
> $cookie = $r->header_in('Set-Cookie');
i actually prefer the headers_in after reading about it.
(personal preference and lazy to boot ;)
> You might also want to take a look at headers_in() (that's PLURAL). It
> is a little more fle
Steffers wrote:
>
> you know, its really funny. We have the book right on our
> shelf, but we are more a 'perl cookbook' sort (need an answer
> then heres sample code).
Use the tool that best fits the situation. I have both books on my
shelf. ;-)
> When I run the Ticket code from chapter 6 i +a
> Drew wrote:
> > Going by your previous example, you should use
> > $cookie = $r->header_in('Set-Cookie');
Quick reality check here -- I'm easy to confuse. =o)
Shouldn't that be
$cookie = $r->header_in('Cookie')
to get cookies the browser sends, and then something like
$r->headers_out
Paul wrote:
>
> > Drew wrote:
> > > Going by your previous example, you should use
> > > $cookie = $r->header_in('Set-Cookie');
>
> Quick reality check here -- I'm easy to confuse. =o)
>
> Shouldn't that be
>
>$cookie = $r->header_in('Cookie')
>
> to get cookies the browser sends, and the
ilto:[EMAIL PROTECTED]]
> Sent: Thursday, June 08, 2000 18:11
> To: Paul
> Cc: modperl
> Subject: Re: Apache, Mod_Perl and Custom Access/Authentication
>
>
> Paul wrote:
> >
> > > Drew wrote:
> > > > Going by your previous example, you should use
&g
Jerrad Pierce wrote:
>
> A server issues Set-Cookie: a client replies with Cookie:
It makes sense now that I think about it. I always use CGI.pm or
Apache::Cookie to get the cookies so I never had to look at the incoming
cookie headers. Live and learn eh?
Well, it's the end of a long day on a l
Drew wrote:
> Well, it's the end of a long day on a long week - does that get me off
> the hook? Note to self: double check your memory next time. :-)
yup, its been a long long week alright.
On the downside, i +still+ cant get the cookies to work,
although after faking a session via telnet it s
"Steffers" <[EMAIL PROTECTED]> writes:
> Drew wrote:
> > Well, it's the end of a long day on a long week - does that get me off
> > the hook? Note to self: double check your memory next time. :-)
>
> yup, its been a long long week alright.
>
> On the downside, i +still+ cant get the cookies to
Steffers wrote:
>
> On the downside, i +still+ cant get the cookies to work,
> although after faking a session via telnet it seems to work
> jst fine. Set-Cookie and everything. It +seems+ to be setting
> the cookie, but Apache is claiming that the browser doesnt
> like them (and yes, i have doub
Vegard Vesterheim wrote:
>
> When dealing with cookie problems, it can be helpful to use a 'HTTP
> protocol sniffer'. You configure your browser to use the sniffer as a
> proxy, which will be sitting between the server and The client and
> allows you to 'listen in' on the HTTP conversation.
>
>
Good morning Drew.
> > On the downside, i +still+ cant get the cookies to work,
> > although after faking a session via telnet it seems to work
> > jst fine. Set-Cookie and everything. It +seems+ to be setting
> > the cookie, but Apache is claiming that the browser doesnt
> > like them (and yes,
Steffers wrote:
> okay okayi seem to be calling the Cookie once...i dont
> +believe+ this. An old piece of code that I wrote in the cgi
> many many moons ago is also doing a redirect
> to a place which is 'locked down' so no one can get access
> (it has a different reason for living ;).
>
>
15 matches
Mail list logo
