-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
question about directive ProxyDirectoryListPolicy #278
Comments
Could you provide the full mod_proxy config you're using (not just screenshots), along with ProFTPD debug logging and the |
Also, it looks like FileZilla is using the |
Yes, you are right. |
Sorry, since I am on the intranet, it is more convenient for me to use screenshotsThe configuration is as follows: |
Hmm. I see some unknown configuration directives in your configuration:
as well as some unknown log messages:
which suggest that you are running with some custom patches/changes. Without knowing that those customizations are, what they do, I cannot say whether they are related to any issues you are seeing. |
… an unrelated issue when running mod_proxy + remote server in a Docker Compose setup. The issue is related to the timing of when we compare the address families of our local bind address vs the remote data address; unfortunately this comparison was occurring _before_ the local bind address variable had been set.
One thing you might try is to disable MLSD support in ProFTPD, so that FileZilla uses
See |
When I use the filezilla client to directly connect to the vsftpd server, the client displays as shown below:
When I use the proxy and configure this #21 directive, the client displays as shown below:
The difference between the above two pictures is that after using the proxy, the file list of the remote site is not output.Can you tell me the reason?
The configuration is as shown below:
The text was updated successfully, but these errors were encountered: