Ha! it turns out I had forgotten to deactivate a Filter. It works great.
I put it online, you can see it in action if you're curious.
1 - Use the login form in the demo section of the site in my sig
2 - navigate to https://legalcase.libremen.com/base/export_raw_data
Thanks to Ed and M
On Fri, 16 May 2025 01:11:48 +0200
Vincent Veyron wrote:
>
> I have a working prototype
>
Well, scratch that, it does work on a slow spinning disk, not on SSD :-\
Also, I'm getting something strange when testing for the presence of a file
before removing it, as in :
if ( -e $r->docume
t; timeout.
>
Thanks for the tip. That lead me to a solution without javascript, nice.
--
Bien à vous, Vincent Veyron
https://legalcase.libremen.com
Open source legal case, contract and insurance claims management software
On Tue, 13 May 2025 22:57:05 -0400
Ed Sabol wrote:
Hi Ed,
>
> Well, the standard way of doing that is you fork a child process to run the
> system command while the parent process loops and prints a period (or
> whatever you prefer) every 1 second (make sure you call f
se, 'postgres') ;
>
>system(@args) == 0 or warn "system @args failed: $!" ;
>
> then waits for the resulting file before proceeding to compress and tar it,
> also with a system() call.
>
> How can I wrap this in a loop that re-sends the 'Building t
by a window.location.href. This wont help your long running
process though since the refresh will trigger another dump and tar. What
you need to do is send the header and flush followed by the system commands
- once rflush has happened the client side will wait forever without a
timeout.
On Tue, May 13, 2025
Apache2::Request is the base and you would at least need that to consume a
request.
The rest are optional and expand on what $r provides. You include them only
if you are using something they are providing.
On Tue, May 13, 2025, 8:37 PM wrote:
> Hello
>
> In my modperl handler, I
Hello
In my modperl handler, I only use Apache2::Request module.
What relations are there between Apache2::Request and the following
modules?
use Apache2::RequestRec ();
use Apache2::RequestIO ();
use Apache2::Connection ();
use APR::Table ();
Should I include them in startup.pl as well as
On Tue, 13 May 2025 14:57:15 -0500
Mithun Bhattacharya wrote:
Hi Mithun,
> Hence if you are writing a mod_perl handler for such an endpoint you return
> success immediately and then start processing the request. In most cases
> this is simply a matter of doing $r->print on the head
Http return codes are relevant only for request with fast response time. It
helps the requestor get a quick status 200 is all good, 3xx something
temporary, 4xx client has made some mistakes and 5xx server faulted.
Unfortunately this design doesn't map well to requests which take
signif
w this is done, I thought one had to send the content with
the headers?
I have a function in my web application which allows users to download the
entirety of their data in the form of a postgresql dump, wrapped in a zip file.
The files are getting bigger, and take more time to generate and downlo
I'm sorry, had not read carefully.
mod_remoteipmodifies the environment variables, so I can imagine that the
get_remote_host method keeps pointing to the Proxy server address
If you can't change the calls with that method, you can try to capture
those calls and replace the value
Hello, mod_perl users!
I am trying to use Apache 2.4 + mod_perl behind a reverse proxy,
which sets the X-Forwarded-For header. Apache itself supports
this via mod_remoteip, which mostly works[1]. However, from the
mod_perl point of view, the remote address is set only in $ENV{REMOTE_ADDR},
On Fri, 18 Aug 2023 22:42:16 -0400
Joe Schaefer wrote:
> The httpd project fucked it up, and won’t unfuck it with a valid release.
>
hhh... Thank you for the information.
Would you say the packages will return to main, eventually, we just don't
The httpd project fucked it up, and won’t unfuck it with a valid release.
On Fri, Aug 18, 2023 at 9:21 PM Vincent Veyron wrote:
>
> Hi list,
>
> I upgraded a machine from Debian Bullseye to Debian Bookworm. Kind of a
> bumpy road, as libapache2-request-perl ended up uninstalle
Hi list,
I upgraded a machine from Debian Bullseye to Debian Bookworm. Kind of a bumpy
road, as libapache2-request-perl ended up uninstalled. I had to add :
deb http://deb.debian.org/debian bookworm-backports main
to my sources.list to re-install libapache2-request-perl and upgrade
t; Also, when running the test script manually from the command line, surely
>> that would bring up a new connection and then at least return the new data.
>>
>> Hell, I even went as far as to drop the table and re-create it - yet when
>> querying via DBI - I still (someh
ual change on the server, so it
isn't visible to other connections.
I thought about this - but surely, restarting *everything* (db +
apache + entire VM) would cause this to fall out.
Also, when running the test script manually from the command line,
surely that would bring up a new connec
nnections.
>
>
> I thought about this - but surely, restarting *everything* (db + apache +
> entire VM) would cause this to fall out.
>
> Also, when running the test script manually from the command line, surely
> that would bring up a new connection and then at least return the n
ut.
Also, when running the test script manually from the command line,
surely that would bring up a new connection and then at least return
the new data.
Hell, I even went as far as to drop the table and re-create it - yet
when querying via DBI - I still (somehow?!) get the old data :|
th->execute();
>>> $vars->{"count"} = $sth->fetchrow_hashref();
>>>
>>> count' => { 'COUNT(*)' => 29 }
>>>
>>> This table is only ever updated manually - so there is no possible way
>>> that the contents
> { 'COUNT(*)' => 29 }
>>
>> This table is only ever updated manually - so there is no possible way
>> that the contents are being updated during these runs - however I also note
>> that the data returned in something like `SELECT * FROM printers` is
>>
hat the contents are being updated during these runs - however I also note
>> that the data returned in something like `SELECT * FROM printers` is
>> different than what I get by running the query directly.
>>
>
> What do you mean by different?
>
>>
>> Annoyin
Hi
This page on perlmonks.org/?node_id=317752 mentions you should name the
count(*) value and then call for the value of that “column”.
I hope that can point you in a good direction
Mike
From: Steven Haigh via modperl
Sent: January 26, 2023 8:56 PM
To: demerphq
Cc: modperl
get by running the query directly.
What do you mean by different?
Annoyingly, even after restarting apache, restarting mariadb, and
even restarting the entire machine, I still see this issue.
That leaves me completely stuck - how can old data be returned -
even after a full machine reboot?
ot;} = $sth->fetchrow_hashref();
>
> count' => { 'COUNT(*)' => 29 }
>
> This table is only ever updated manually - so there is no possible way
> that the contents are being updated during these runs - however I also note
> that the data returned in something l
during these runs - however I also
note that the data returned in something like `SELECT * FROM printers`
is different than what I get by running the query directly.
Annoyingly, even after restarting apache, restarting mariadb, and even
restarting the entire machine, I still see this issue.
T
Its got a GIL and it cores frequently and it’s not exposing much of the
httpd/apr. It’s not that popular compared to wsgi.
On Fri, Aug 19, 2022 at 10:20 PM pengyh wrote:
> I know perl and python a bit well, most time use both of them for work.
> besides mod_perl, there is also mod_python
That is because unlike mod_perl mod_python doesn't integrate deeply into
Apache and you can't extend every HTTP request cycle phases.
Only two programming languages integrate that deeply - C and Perl.
On Fri, Aug 19, 2022, 7:19 PM pengyh wrote:
> I know perl and python a bit we
I know perl and python a bit well, most time use both of them for work.
besides mod_perl, there is also mod_python.
do you know what's the difference between them?
I never heard people using mod_python to make some jobs.
Thanks
2022.
Any project that still uses the CMS in any way shape or form, MUST migrate
to another build and publish method.
Any project using ci.apache.org for the building and testing/publishing of
CI builds MUST also migrate away to another CI - the direct replacement is
ci2.apache.org the new Buildbot
gt; would display something useful. Personally, this is always the first link I
> check when I want to submit a patch or issue on something Perl-related.
> Compare https://metacpan.org/dist/mod_perl/contribute to
> https://metacpan.org/dist/DBD-Pg/contribute, e.g. This file should docum
an.org/dist/mod_perl/contribute to
https://metacpan.org/dist/DBD-Pg/contribute, e.g. This file should document how
to check out the source code repository, how and where to submit patches, where
to file issues, etc. I think it would be extremely useful, and it doesn't need
to be
On Mon, 8 Nov 2021 at 18:28, Thomas Bartosik wrote:
>
> Hi!
>
> Up until Ubuntu 18.04 LTS or Debian 9, a perl service (eprints.org) and a PHP
> service (nextcloud) worked smoothly next to each other on Apache with mod_php
> and mod_perl2.
>
> However, on Ubuntu 20.04 LT
Hi!
Up until Ubuntu 18.04 LTS or Debian 9, a perl service (eprints.org) and a PHP
service (nextcloud) worked smoothly next to each other on Apache with mod_php
and mod_perl2.
However, on Ubuntu 20.04 LTS, or Debian 10, as soon as I enable mod_perl2,
setlocale() on nextcloud does not seem to
for as you refactor your code for mod_perl, including
the problem with __DATA__ that you had (from a later post). In fact, the
whole book is a great read. I highly recommend skimming through it and
reading in detail as you see fit.
On 2/6/2021 4:59 PM, Steven Haigh wrote:
Hi all,
So for many
On Fri, Feb 12, 2021 at 05:15:29PM +0100, André Warnier (tomcat/perl) wrote:
> My comment was just basically so as to avoid the case where someone else
> would later be searching the archives of this mailing list for information
> about DBI, and never find these (useful for DBI) posts, be
My comment was just basically so as to avoid the case where someone else would later be
searching the archives of this mailing list for information about DBI, and never find
these (useful for DBI) posts, because DBI is not in the subject.
On 12.02.2021 00:51, Chris wrote:
On Thu, Feb 11, 2021
On Thu, Feb 11, 2021 at 09:52:16AM +0100, André Warnier (tomcat/perl) wrote:
> Isn't this discussion about connection pools and firewalls etc getting a bit
> far from the initial subject of the thread ?
Perhaps. But this has become a pretty low volume mailing list.
This "thread&
Isn't this discussion about connection pools and firewalls etc getting a bit far from the
initial subject of the thread ?
On 09.02.2021 23:03, Mithun Bhattacharya wrote:
I would consider mine a small setup on an internal network and I have used both Sybase and
SQL Server. In our case the
As a long time Oracle DBA and perl mangler I have refrained from joining
this conversation until now.
Connection caching is a configuration option in DBI, not a coding
requirement. For web servers it is a single line edit in startup.pl
import DBICache versus import DBI if I recall incorrectly
I would consider mine a small setup on an internal network and I have used
both Sybase and SQL Server. In our case the DBA's preferred us to remain
connected rather than make too many connections - we need DB access in
bursts - it could be quiet for more than an hour and then suddenly we
The advantage of the web proxy is not from securing your app - although there
are things you can do on the reverse proxy to secure less secure apps
It's main advantage is that it doesn't run a large software stack - and so it
makes it harder for people to compromise your front en
Mithun,
I’m not sure on what scale you work – but these are from experience in sites
with small to medium load – and we rarely see an appreciable gain in using
cached or pooled connections, just the occasional heartache they cause.
If you are working on small applications with a minimal number
> On 9 Feb 2021, at 19:16, Rafael Caceres wrote:
>
> Another thing that can be done is keep the app server + DB inside your LAN
> and place a reverse proxy on your DMZ, that adds some level of protection.
Not really - the only protection is if all your apis or web pages are s
Another thing that can be done is keep the app server + DB inside your LAN and
place a reverse proxy on your DMZ, that adds some level of protection.
Rafael
On Feb 9, 2021, 2:08 PM -0500, Clive Eisen , wrote:
On 9 Feb 2021, at 18:45, James Smith wrote:
It doesn't matter what db
> On 9 Feb 2021, at 18:45, James Smith wrote:
>
> It doesn't matter what db - and whether you wrap it in eval it is a problem
> (postgres has a similar problem - the one with least problems is MySQL) - if
> you have a secure environment where your databases are in a f
It doesn't matter what db - and whether you wrap it in eval it is a problem
(postgres has a similar problem - the one with least problems is MySQL) - if
you have a secure environment where your databases are in a firewalled zone it
will happen to all of them... It's a nasty bit of
te:
>
> Hi James,
>
> > DBI sharing doesn't really gain you much - and can actually lead you
> into a whole world of pain. It isn't actually worth turning it on at all.
> >
>
> Never had a problem with it myself in years of using it, but I wrap my
> queries in
On Sun, 7 Feb 2021 20:21:34 +
James Smith wrote:
Hi James,
> DBI sharing doesn't really gain you much - and can actually lead you into a
> whole world of pain. It isn't actually worth turning it on at all.
>
Never had a problem with it myself in years of using it, bu
s can leak between runs?
Is coding to normal 'use strict; use warnings;' standards good enough?
Hi. Read this, carefully :
http://perl.apache.org/docs/2.0/user/troubleshooting/troubleshooting.html#Variable__x_will_not_stay_shared_at
In particular the example below "An Easy Br
That is a good sign – I would run with brutal at least once and see what it
throws up
We tend to ignore a couple of the warnings – one is postfix if/unless and the
other is multiline strings {we embed a lot of simple HTML templates in code and
it means I can make the HTML readable when
On Mon, Feb 8, 2021 at 09:13, James Smith wrote:
Use perl-critic this will find most of the nasties that you have the
classic is:
Thanks for the tip! I have no idea how long I've been writing stuff in
perl - and I never knew of this!
I ran it with the -3 option - which I figure is a
{condition};
or
my $var = {condition} ? {code} : ‘’;
From: Steven Haigh
Sent: 08 February 2021 09:09
To: modperl@perl.apache.org
Subject: Re: Moving ExecCGI to mod_perl - performance and custom'modules'[EXT]
On Sun, Feb 7, 2021 at 15:17, Chris
mailto:cpb_mod_p...@bennettconstruction.u
On Sun, Feb 7, 2021 at 15:17, Chris
wrote:
Just remember to always write clean code that resets variables after
doing tasks.
I'm a bit curious about this - whilst I'm still testing all this on a
staging environment, how can I tell if things can leak between runs?
Is coding to normal 'use st
I meant between requests in the same thread – it uses persistent connections
which are bad in a number of ways {e.g. fun with locking if you use it and your
script dies halfway through, keeps too many connections open and can block the
database, has issues with secure set ups {firewall between
what's DBI sharing? do you mean Apache::DBI?
Does perl has Java similar DB connection pool?
Thanks.
On Mon, Feb 8, 2021, at 4:21 AM, James Smith wrote:
> DBI sharing doesn't really gain you much - and can actually lead you into a
> whole world of pain. It isn't actually w
ur gotchas...
Try
my $admin = 1 if $user_is_logged_in and $user eq 'admin';
may seem innocent in as script and compiles even under use strict... but now
put this in a loop
1st request user is logged in and is admin - this gets set to true.
2nd request user isn't logged in - but
developing SQL in
oracle but people developing Oracle) scratching their heads over things like
this and not being able to come up with a solution…..
We’ve discovered lots of interesting side effects with connection pooling when
using over a secure network – e.g. the Oracle client doesn’t like
it.
You can mix Registry and handlers together without any problems.
Just remember to always write clean code that resets variables after
doing tasks. The same code runs multiple times. Variables might retain
old values. It's a good habit to keep for all perl code, even outside of
mod_perl.
I con
DBI sharing has it's own issues but in most use cases it does a pretty good
job and keeps the DBA's happy - that is very important ;)
On Sun, Feb 7, 2021 at 2:23 PM James Smith wrote:
> DBI sharing doesn't really gain you much - and can actually lead you into
> a whole wo
We're in a similar situation with 20-40 databases per server. We use
PGBouncer for connection pooling.
On Sun, Feb 7, 2021 at 2:23 PM James Smith wrote:
> DBI sharing doesn't really gain you much - and can actually lead you into
> a whole world of pain. It isn't actually w
DBI sharing doesn't really gain you much - and can actually lead you into a
whole world of pain. It isn't actually worth turning it on at all.
We use dedicated DB caching in the cases where we benefit from it as and when
you need it (low level caching database)...
Although milag
On Sun, 07 Feb 2021 23:58:17 +1100
Steven Haigh wrote:
>
> I haven't gotten into the preload or DBI sharing yet - as that'll end
> up needing a bit of a rewrite of code to take advantage of. I'd be open
> to suggestions here from those who have done it in the past to save me
> going down some
me per request: 207.140 [ms] (mean)
> Time per request: 6.473 [ms] (mean, across all concurrent requests)
>
> Running some benchmarks across various parts of my site made me realise I
> also had some RewriteRules in the apache config that still had H=cgi-script -
> changed
s in the apache config that still had
H=cgi-script - changed those to H=perl-script and saw similar
improvements:
ExecCGI - Requests per second:11.84 [#/sec] (mean)
mod_perl - Requests per second:130.97 [#/sec] (mean)
That's quite some gains for a days work.
--
hy - but I stripped all the templates
out and put them in a file instead and re-wrote that bit of code, and
things started working.
I had to fix a few lib path issues, but after getting my head around
that, most things seem to work as before - however I don't notice much
of an improveme
lly
a gain from using them}
It suggests you use ModPerl/PerlRunPrefork – as this does an additional step to
cd to the script directory – which might be your issue….
From: Steven Haigh
Sent: 07 February 2021 01:00
To: modperl@perl.apache.org
Subject: Moving ExecCGI to mod_perl - performance and custo
Is the url in your signature the website? It looks a beautiful UI design.
And you can try this method:
https://metacpan.org/pod/ModPerl::Registry
Thanks.
On Sun, Feb 7, 2021, at 8:59 AM, Steven Haigh wrote:
> Hi all,
>
> So for many years I've been slack and writing perl scripts
Hi all,
So for many years I've been slack and writing perl scripts to do
various things - but never needed more than the normal apache +ExecCGI
and Template Toolkit.
One of my sites has become a bit more popular, so I'd like to spend a
bit of time on performance. Currently, I
On Sep 7, 2020, at 11:28 AM, Andrew Green wrote:
> I’d like to be able to set SameSite=Strict on a cookie generated using
> Apache2::Cookie, but if I simply try to set that parameter, I get the
> following error:
>
> Can't locate object method "SameSite" via package "Apache2::Cookie”
>
> Is
Hi all,
I’d like to be able to set SameSite=Strict on a cookie generated using
Apache2::Cookie, but if I simply try to set that parameter, I get the following
error:
Can't locate object method "SameSite" via package "Apache2::Cookie”
Is it possible?
Many thanks,
Andrew.
Hi
on 2020/1/9 14:14, Mithun Bhattacharya wrote:
This is for PHP but it still applies.
https://www.geeksforgeeks.org/what-is-the-difference-between-http_host-and-server_name-in-php/
This is good reference. Thanks.
This is for PHP but it still applies.
https://www.geeksforgeeks.org/what-is-the-difference-between-http_host-and-server_name-in-php/
On Wed, Jan 8, 2020 at 8:39 PM Wesley Peng wrote:
> Hello
>
> For HTTP headers, what's difference between HTTP_HOST and SERVER_NAME?
>
> I wa
Hello
For HTTP headers, what's difference between HTTP_HOST and SERVER_NAME?
I was long time confused about them.
Thanks.
rial release for
> testing?
>
> I have not found it on https://metacpan.org/release/libapreq2 so perl
> community have not noticed about it.
>
> > > but regardless there was
> > > very little effective difference between that and 2.13 - mostly around
> >
On Oct 20, 2019, at 7:35 PM, Edward J. Sabol wrote:
> I've successfully ported Apache2::AuthCookieDBI's group
> authorization to work with Apache 2.4.x. It works on my system, and I am
> now looking at submitting a pull request on GitHub for this issue.
In case anyone i
acpan.org/release/libapreq2 so perl
community have not noticed about it.
> > but regardless there was
> > very little effective difference between that and 2.13 - mostly around
> > tests, docs and build scripts. 2.13 should run just fine on 2.4
>
> Somehow, it only came to my at
On Feb 12, 2019, at 2:25 PM, Edward J. Sabol wrote:
> Hello! I have a project that has successfully used Apache2::AuthCookieDBI
> with mod_perl on Apache 2.2 and Apache 2.0 before that for many years. For
> various reasons, we are looking at moving this project to a new system that
>
menting my workaround I found that it seems
to make a difference when things get loaded as well. For example I'm
loading things now during server startup and Digest::SHA instantly
segfaulted in this scenario, while it didn't in the former setup when
letting mod_perl compile automatically per
I'm surprised that you're able to use the threaded MPM at all. The only MPM
we're able to make work with our application is prefork. As far as I'm
aware, Perl itself and its core libraries are thread safe but because Perl
spent the last 3 decades without official threading
Le mer. 31 juil. 2019 à 19:33, Thorsten Schöning
a écrit :
>
> Hi all,
>
> I'm struggling for 2+ years[1][2] with a problem using mod_perl on
> Linux which I was finally able to reproduce on Windows as well.
Hello Thorsten,
we face the same issues with mod_perl in LemonLDAP::NG
(https://lemonlda
80] AH00491: caught SIGTERM, shutting down
Disabling mod_perl makes the problem go away, so syntax errors itself
are pretty unlikely anyway. Additionally even with enabled mod_perl
the error doesn't occur always, only pretty often, but if it occurs
once and some time later not anymore or the ot
I see that the status has been changed to "resolved/fixed" just
today. That's really fast turn-around, which is always good to see.
> Hi,
>
> an issue has been reported between httpd 2.4.39 and mod_perl 2.0.10.
> See https://bz.apache.org/bugzilla/show_b
Hi,
an issue has been reported between httpd 2.4.39 and mod_perl 2.0.10.
See https://bz.apache.org/bugzilla/show_bug.cgi?id=63516.
It is under investigation, but any input from the mod_perl community is
welcome :)
Thx in advance.
Christophe Jaillet
On Feb 21, 2019, at 5:22 AM, Vegard Vesterheim
wrote:
> I registered a ticket against Apache2-AuthCookieDBI regarding this issue
> a long time ago:
>
> https://rt.cpan.org/Public/Bug/Display.html?id=106663
>
> We do not use this any longer. But, given that the ticket is still open,
> I wonder i
s, as well as reading the source code of apache itself. I'm
not sure I found any definitive guide on the changes when I did this,
and it involved a good deal of research at the time.
Thanks much for putting that together, I found it an invaluable (and
unique) resource in figuring out how
On 2/21/19 3:41 AM, André Warnier (tomcat) wrote:
> 1) the "authz" function is now called *first* (before any authentication
> module has been called - even non-perl add-on ones),
> and
> 2) it *can* be called 2 or more times during the same request cycle
> and
Yes,
d to change it to use
> Apache2_4::AuthCookie base, as eventually I managed to get all of the
> changes needed to work togehter in Apache2::AuthCookie. I left
> Apache2_4::AuthCookie for historical reasons, and in case further issues
> came up that would require more changes that were 2.4
n is now called *first* (before any authentication module has been
called - even non-perl add-on ones),
and
2) it *can* be called 2 or more times during the same request cycle
and
3) the "authz" function, in Apache 2.4, is much more "at the mercy" of whatever
Authentication modul
On Thu, Feb 21, 2019 at 02:35:22AM +, Jie Gao (j@sydney.edu.au) wrote:
> * Jobst Schmalenbach wrote:
>
> Not sure how you went with this issue, but you might want to try this instead:
>
>
> Require user USER1 USER2
>
> Require ip 127.0.0.1
> Require host localho
* Jobst Schmalenbach wrote:
> Date: Wed, 20 Feb 2019 12:33:22 +1100
> From: Jobst Schmalenbach
> To: modperl@perl.apache.org
> Subject: Apache upgrade 2.2 -> 2.4 and "PerlAuthenHandler
> Authen::Simple::IMAP"
> User-Agent: Mutt/1.9.1 (2017-09-22)
>
> I po
On Wed, Feb 20, 2019 at 05:56:48PM -0500, Edward J. Sabol wrote:
> Any pointers to a working AuthzProvider written in Perl (like for the
> "species" one) in your examples? It's not perfectly clear to me how to
> go about that.
I wrote one for CAS auth a while back:
https://github.com/pbhenson/Ap
r historical reasons, and in case further issues
> came up that would require more changes that were 2.4 exclusive.
Impressive! And good to know.
> If you aren't doing anything fancy with `require` directives, you likely
> don't need to worry about creating an Authz provider, whic
rd query would not come up and the IMAP module would not be required.
>
> On Wed, Feb 20, 2019 at 5:11 AM Jobst Schmalenbach
> > On Tue, Feb 19, 2019 at 06:14:53PM -0800, Paul B. Henson (hen...@acm.org)
> > > On 2/19/2019 6:02 PM, Jie Gao wrote:
> >
> > Need to
use
Apache2_4::AuthCookie base, as eventually I managed to get all of the
changes needed to work togehter in Apache2::AuthCookie. I left
Apache2_4::AuthCookie for historical reasons, and in case further issues
came up that would require more changes that were 2.4 exclusive.
If you aren't
the
changes needed to work togehter in Apache2::AuthCookie. I left
Apache2_4::AuthCookie for historical reasons, and in case further issues
came up that would require more changes that were 2.4 exclusive.
If you aren't doing anything fancy with `require` directives, you likely
don't need t
the
> module
> > does not support it.
> >
> > Authen::Simple::Apache, not Authen::Simple::IMAP itself. That one was
> last
> >
>
> There are actually a few issues here and it's not
>
> - Authen::Simple::Apache
> - Authen::Simple::IMAP
>
> It has to
le was in 2009; Apache 2.4 was released in
> 2012, so without even looking at the code I am fairly confident the module
> does not support it.
>
> Authen::Simple::Apache, not Authen::Simple::IMAP itself. That one was last
>
There are actually a few issues here and it's not
- Auth
ched CPAN directly rather than relying on
>
> :).
Is there nothing else that provide IMAP conneciton/login/query?
Jobst
--
You seem (in my (humble) opinion (which doesn.t mean much)) to be (or possibly
could be) more of a Lisp programmer (but I could be (and probably am) wrong)
|
1 - 100 of 3717 matches
Mail list logo
