TJ Saunders
TJ Saunders
Indeed, I've been pondering how to implement such a feature in `mod_proxy` for a while; see, for example, Issue #186
Can some other script, outside of `mod_proxy`, call that external remote API to obtain the necessary data, and then insert/provision that data into a static file or SQL statement that...
You might be able to do this sort of thing already, using [`ExecOnConnect`](http://www.proftpd.org/docs/contrib/mod_exec.html#ExecOnConnect)...
Well, I guess `ExecOnConnect` would work _if_ your remote API returned data based on the client's IP address. For a per-user thing, you'd use [`ExecBeforeCommand`](http://www.proftpd.org/docs/contrib/mod_exec.html#ExecBeforeCommand), _e.g.: ExecEngine on ExecLog ......
Why does it feel like a hack? An "exec" type functionality is precisely what the `mod_exec` module provides; why duplicate it (but differently) in `mod_proxy`?
The issue of exec not failing, and failing to add to a file or SQL, are the same either way. Having mod_exec do this, or mod_proxy do this, does not...
I wonder if this is related to https://github.com/proftpd/proftpd/issues/959. Is your FTPS client using TLSv1.3, perhaps? Hmm...or maybe it's not related to FTPS as well. I'll have to see if I...
Hmm. I'm not able to reproduce this locally. @mikepultz is still an issue for you, using the latest `mod_proxy` code?
If there's nothing more to add to this ticket, I'd like to close it.
Yes, please do file a separate issue for the compilation error you're encountering; I'd like to address that as well.