Ken Williams wrote:
[EMAIL PROTECTED] (allan) wrote:
im aware of the head/HEAD problem that comes with LWP on mac osX and
have therefore copied a binary head that ken williams sent me into
/usr/bin and moved the lwp head into /usr/local/bin.
Looks like that problem still isn't fixed, as
[EMAIL PROTECTED] (allan) wrote:
one thing: i have discovered that another problem i have had since
upgrading to perl 5.6.1 might be interfering with the one in this topic
(im not sure though - it is concerning setenv)
look at this new fresh terminal window:
[localhost:~] aju% which head
thanks again
i did something similar with that lwp-head before i read your reply, but
somewhat more stupid:
rm HEAD
(!)
in fact i have now tested mod_perl with only oks and skipped on this
platforms and installed as well with no complaints whatsoever.
so i guess im almost there (im posting
The uploaded file
Apache-AuthenLDAP-0.60.tar.gz
has entered CPAN as
file: $CPAN/authors/id/C/CG/CGILMORE/Apache-AuthenLDAP-0.60.tar.gz
size: 8176 bytes
md5: 07405d95c2e62f5ce20f3dc067317755
No action is required on your part
Request entered by: CGILMORE (Christian Gilmore)
Request
The uploaded file
Apache-AuthzLDAP-0.60.tar.gz
has entered CPAN as
file: $CPAN/authors/id/C/CG/CGILMORE/Apache-AuthzLDAP-0.60.tar.gz
size: 9718 bytes
md5: ee2f18984cea35f0c2c139c25a255526
No action is required on your part
Request entered by: CGILMORE (Christian Gilmore)
Request
The product you are asking about is Commerce Server, which includes the
Creditor component, Apache, covalent_ssl, mod_perl, etc.
http://www.covalent.net/products/commerce/
Hope that helps,
Bill
- Original Message -
From: Adam Prime [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent:
From: [EMAIL PROTECTED]
any Proxy operator can do this with any non-SSL connection. One can spy session
ids in the URL, in the GET-parameters and the POST-parameters, also cookies and
basic auth passwords, also passwords in html forms - and every bit of data
that's send back.
Oh, and
On Fri, May 25, 2001 at 10:03:04AM -0700, Jonathan Hilgeman wrote:
Now, I'm assuming that Apache has full access to these incoming packets.
Therefore, they must also have access to this invisible identifier. Is it
possible to extract that identifier somehow by tinkering with Apache?
Most NAT
Greetings,
This note is in reference to your site listing for
http://perl.apache.org/stories/
You can check your listing by simply clicking here:
http://www.bigwhat.com/asp/s.asp?b=au=http://perl.apache.org/stories/
If any portion of your listing is missing or inaccurate
your site will not
