Re: mod_ftp segaults on rheloids

[Benjamin Lefoul]

On Fri, 2016-11-11 at 12:10 -0600, William A Rowe Jr wrote:
> On Fri, Nov 11, 2016 at 2:24 AM, Benjamin Lefoul  se.se> wrote:
> > Is this list still active?
> > Maybe it was not the right place to ask about mod_ftp?
> 
> It is the place to ask, and was on my list to respond to your
> question...
> sorry I'm overwhelmed with other code this week.
> 
> The last 'release' is quite dated, and several things changed within
> httpd 2.4 that prove incompatible with the last official mod_ftp
> 0.9.6
> release. I did try to push out another release, but it never got
> enough
> votes to be 'released' by the community, and since has undergone
> a number of bug fixes to work with the current httpd 2.4.23 (although
> it should still be compatible with an older httpd release like
> 2.4.6.)
> 
> http://svn.apache.org/repos/asf/httpd/mod_ftp/trunk/
> is the repository of the current source code. The primary defect I'm
> aware of in an incompatibility with mod_ftp and the httpd core that
> prevents us from successfully serving FTP Explicit SSL connections.
> An implicit SSL connection, e.g. ftps on port 990 (using TLS from
> the 
> time of connecting) is functional.
> 
> Once other httpd projects are wrapped up, I'm coming back to httpd
> 2.4 and mod_ftp to figure out how to get Explicit SSL functioning
> again.
> If you would grab the latest development code I'd love to read about
> your success or any defects you encounter.
> 
> Cheers,
> 
> Bill

Thanks very much for your response and for your work.
A functional FTP module is still of interest for many.
I'll try to do my best to help and give you feedback when I have time.

Benjamin Lefoul

> 
>  
> 

Re: module advice

[Joseph Schaefer]

Use libapreq2

Sent from my iPhone

> On Nov 13, 2016, at 5:08 PM, Mark Blackman  wrote:
> 
> Hi,
> 
> Not sure if this is the right mailing list for this question, and feel free 
> to redirect me if so, however, if I want to write a module to examine an HTTP 
> POST body and execute some action with the contents of the body, but only if 
> the body matches some condition, should that be done with an input filter, 
> taking a copy of the body and then end of the request, doing the matching 
> and/or execution of the action? Or is there some way to plant a hook that 
> gets executed after all the input filters have run and I just have the  whole 
> request body sitting there ready for examination?
> 
> Currently, I believe an input filter is required to copy the request as it 
> comes in, but it might be cleaner to just execute some code after the body 
> has been received if practical.
> 
> Cheers,
> Mark

module advice

[Mark Blackman]

Hi,

Not sure if this is the right mailing list for this question, and feel free to 
redirect me if so, however, if I want to write a module to examine an HTTP POST 
body and execute some action with the contents of the body, but only if the 
body matches some condition, should that be done with an input filter, taking a 
copy of the body and then end of the request, doing the matching and/or 
execution of the action? Or is there some way to plant a hook that gets 
executed after all the input filters have run and I just have the  whole 
request body sitting there ready for examination?

Currently, I believe an input filter is required to copy the request as it 
comes in, but it might be cleaner to just execute some code after the body has 
been received if practical.

Cheers,
Mark