Project

General

Profile

[Solved] Pass raw URL through mod_proxy (equivalent to Apache's "nocanon")

Added by johnnymayhew28 over 1 year ago

Hi,

I am running lighttpd as a reverse proxy in front of a matrix homeserver, which requires the proxy to pass the raw URL to the backend (i.e. without canonicalizing it, without decoding the URL-encoded characters, etc).

In Apache the setting for this is nocanon, documented here

Is there a way to do this with lighttpd?

Currently doing curl https://mywebsite.com/path_with_%40_in_it is passed to the backend as https://mywebsite.com/path_with_@_in_it (checked with netcat on the server)

System details

Running on raspberry pi, raspbian bullseye
version: lighttpd/1.4.59 (ssl)


Replies (6)

RE: Pass raw URL through mod_proxy (equivalent to Apache's "nocanon") - Added by gstrauss over 1 year ago

Is there a way to do this with lighttpd?

Yes, there is. What did you search for in the lighttpd documentation?

RE: Pass raw URL through mod_proxy (equivalent to Apache's "nocanon") - Added by johnnymayhew28 over 1 year ago

I have looked at the mod_proxy docs page, i have also searched for "nocanon" and "raw url", "raw proxy" etc. to no avail.

I have been struggling with this issue for several weeks now :/

Could you tell me how I can do this?

RE: Pass raw URL through mod_proxy (equivalent to Apache's "nocanon") - Added by gstrauss over 1 year ago

I have been struggling with this issue for several weeks now :/

You could read this entire site in much less time. Clearly, you have not.

Hint, I provided a link to lighttpd documentation.
You say that you have looked at mod_proxy configuration options. Clearly you have overlooked other options elsewhere.

RE: Pass raw URL through mod_proxy (equivalent to Apache's "nocanon") - Added by johnnymayhew28 over 1 year ago

I can't read very fast but that's beside the point.

If you could give me some more specific pointer than just the documentation writ large i would appreciate it, there are a whole lot of pages on the wiki, many of which i have read at this point. We have been running lighttpd for nearly a year and have a non-trivial setup, involving SSL, CGI, multiple domains, aliasing, rewriting, proxying. I have looked through the module listings on the wiki, none of which jump out to me as relevant beside mod_proxy. I know that the wiki is there, i just don't know which part of it i should be searching in, and would appreciate a pointer or two.

RE: Pass raw URL through mod_proxy (equivalent to Apache's "nocanon") - Added by gstrauss over 1 year ago

If you have not looked at the page labelled "Configuration: Options", then you might be beyond help.

Basic logic: you shared that you read mod_proxy doc and that you did some basic keyword search which did not turn up results for you. Since you omitted sharing any other information, that suggests to me that you have failed to actually read the documentation starting at link that I have now provided three times: lighttpd documentation

I try to help people who try to help themselves, not those who lie about their effort. You failed a few simply keyword searches. That barely constitutes 5-10 mins to search and read the mod_proxy page. You have been grossly incompetent if you have spent weeks on this; I am certain that you have not spent such time since I do not think you are that stupid. (However, that much time may have elapsed since you started "working" on this problem, though my definition of "work" and your definition of "work" likely differ substantially.) Please make an effort to do a little bit more "work". Read the doc and ask a specific and intelligent question if something specific is not clear in the documentation. Hint: you have failed to consider synonyms of your keyword searches (at least those you shared). Did you really not wonder why your searches for Apache-specific keywords failed?

RE: [Solved] Pass raw URL through mod_proxy (equivalent to Apache's "nocanon") - Added by gstrauss over 1 year ago

server.http-parseopts HTTP request parsing and normalization options

Why have you gotten a rude response? Because you exaggerated your effort and repeatedly failed to demonstate that you read a few words of documentation. Any future posts by you are likely to be ignored or receive a simple RTFM, or another rude response.

This site is not for your benefit. People who make an effort generally get a much kinder response. You're just a freeloader. "I can't read very fast but that's beside the point." You should stop feeling sorry for yourself and make a greater effort.

    (1-6/6)