https://bz.apache.org/bugzilla/show_bug.cgi?id=66341
Bug ID: 66341
Summary: mod_proxy_ftp documentation says it supports
user/pass. Error AH02422 says it does not
Product: Apache httpd-2
Version: 2.4-HEAD
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Documentation
Assignee: docs@httpd.apache.org
Reporter: briandking@gmail.com
Target Milestone: ---
In the documentation here:
https://httpd.apache.org/docs/2.4/mod/mod_proxy_ftp.html
It says:
For a personal login with a specific username, you can embed the user name
into the
URL, like in:
ftp://username@host/myfile
... but when using mod_proxy_ftp through curl and supplying a URL with a
username/password (even ftp://anonymous:abc123@server/path), the client will
get a "400 BAD REQUEST" response, and the apache error logs will show:
... [core:debug] [pid 3024:tid 140574807373568] protocol.c(895): [client
1.2.3.4:5] AH02422: HTTP Request Line; URI must not contain a username/password
Since the error specifically says you can't use a username/password, I assume
that is intentional and the documentation is wrong, rather than a bug in
mod_proxy_ftp not implementing the feature correctly.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Bug ID: 66341
Summary: mod_proxy_ftp documentation says it supports
user/pass. Error AH02422 says it does not
Product: Apache httpd-2
Version: 2.4-HEAD
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Documentation
Assignee: docs@httpd.apache.org
Reporter: briandking@gmail.com
Target Milestone: ---
In the documentation here:
https://httpd.apache.org/docs/2.4/mod/mod_proxy_ftp.html
It says:
For a personal login with a specific username, you can embed the user name
into the
URL, like in:
ftp://username@host/myfile
... but when using mod_proxy_ftp through curl and supplying a URL with a
username/password (even ftp://anonymous:abc123@server/path), the client will
get a "400 BAD REQUEST" response, and the apache error logs will show:
... [core:debug] [pid 3024:tid 140574807373568] protocol.c(895): [client
1.2.3.4:5] AH02422: HTTP Request Line; URI must not contain a username/password
Since the error specifically says you can't use a username/password, I assume
that is intentional and the documentation is wrong, rather than a bug in
mod_proxy_ftp not implementing the feature correctly.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org