Subj : dlreq for web download
To   : opicron
From : Zip
Date : Mon Apr 21 2025 01:04 pm

Hello opicron!

Thank you for your reply!

On 21 Apr 2025, opicron said the following...

 op>  Zi> I like the HTTP --> HTTPS conversion, too (as Mystic doesn't let one 
 op>  Zi> that in the config). =)

 op> Ohh awesome that you noticed. I pulled my hair out trying to do a reverse
 op> proxy. Then I figured, dont fight https just add a little javascript to
 op> update the urls in the html :)..

Speaking of HTTPS, I see that you have an nginx serving the dlreq page over
HTTPS. How do you make nginx preserve the client IP when forwarding the
request to Mystic's web server? (As dlreq checks the client IP and refuses to
serve anything if the IP doesn't match.)

I have HTTP on port 61080 leading directly to the Mystic HTTP web server, and
similarly HTTPS on port 61443 leading to the Mystic HTTPS web server, and I'm
experimenting a little with Apache (which runs all HTTPS stuff with the
"real" SSL cert) to proxy certain URLs internally to 61443, but the client IP
as seen by Mystic's web server will always be the loopback interface, so dlreq denies the download requests when clicking on the file links.

Could be one of those things that are easy to do with nginx, but less so with
Apache. :)

(Hmm, maybe I would need to let Apache handle 61080 as well so that the
"initial" dlreq requests comes from the loopback interface... Which would
trash the client IP checking ability of dlreq, but anyway...)

Thanks in advance!

Best regards
Zip

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
 * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

.