I've gotten AuthAny to an acceptable state for review. It can be downloaded
from the demo site:
https://authany.cirg.washington.edu/download/
If you would like to install it, please be sure to read the "README".
There are a couple of problems with this release:
1) I created a "post-install.pl"
Hi all,
I've been playing around with modperl and attributes. Below is the
module I am experimenting with.
When I start up the server I see the warnings coming from the
MODIFY_CODE_ATTRIBUTES routine.
However, when I fetch the url associated with the handler, it reports
that ATTRS = {}.
Moreover,
Hi Torsten,
So is this what you are suggesting...
Define $MAX_SIZE to be the largest length of POSTed data you will accept.
For modperl <= 2.0.4 just use a single read and hope for the best:
$r->read($buf, $MAX_SIZE);
For modperl > 2.0.4 ( >= 2.0.5?) using this while-loop works:
my $buf =
On Wednesday, April 27, 2011 17:40:11 E R wrote:
> What's the proper way to read in the posted content from a request?
>
> Using this Google code search:
>
> http://www.google.com/codesearch?q=lang%3Aperl+%5C%24r-%3Eread.*length
> &hl=en
>
> I see instances of:
>
> $r->read($line, $r->headers
Hi,
What's the proper way to read in the posted content from a request?
Using this Google code search:
http://www.google.com/codesearch?q=lang%3Aperl+%5C%24r-%3Eread.*length&hl=en
I see instances of:
$r->read($line, $r->headers_in->get('Content-length'));
and also loops like:
while ( $
Don't stay beholden to the mp1 way of compiling statically unless you
have a really good reason to do so and know what you are doing. If
you are deploying in a server based environment, compile as a shared
object, or use the rpms. No reason to make life extra hard for
something that shouldn't tak
