On 2/25/2019 2:57 PM, Randolf Richardson wrote:
On 2/25/2019 2:28 PM, Randolf Richardson wrote:
[sNip]
As long as one isn't relying on the client's dynamic TCP port number
from $r->connection->remote_addr->port for anything (as I've
discovered no longer works in the current release of
> On 2/25/2019 2:28 PM, Randolf Richardson wrote:
> > [sNip]
> >>> As long as one isn't relying on the client's dynamic TCP port number
> >>> from $r->connection->remote_addr->port for anything (as I've
> >>> discovered no longer works in the current release of mod_perl2),
> >>> updating to the n
On 2/25/2019 2:28 PM, Randolf Richardson wrote:
[sNip]
As long as one isn't relying on the client's dynamic TCP port number
from $r->connection->remote_addr->port for anything (as I've
discovered no longer works in the current release of mod_perl2),
updating to the newest mod_perl2 sho
[sNip]
> > As long as one isn't relying on the client's dynamic TCP port number
> > from $r->connection->remote_addr->port for anything (as I've
> > discovered no longer works in the current release of mod_perl2),
> > updating to the newest mod_perl2 should ultimately be relatively
> > problem-
On 2/24/2019 4:44 PM, Randolf Richardson wrote:
On 2/22/19 10:54 AM, Matthias Schmitt wrote:
I doubt that you will be able to compile mod_perl 1.x with newer compilers and
operating systems.
Hold my beer :).
[sNip]
I have a Makefile that does all of this. I suppose I could publish
it on
