[GH-ISSUE #64] Serving SPFtoolbox over HTTPS with Reverse proxy (Traefik, NPM) #25

New issue

Closed

opened 2026-02-25 21:30:51 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 21:30:51 +03:00

Owner

Originally created by @jaska087 on GitHub (Jul 21, 2023).
Original GitHub issue: https://github.com/charlesabarnes/SPFtoolbox/issues/64

Hi.

Just a weird issue. Serving SPFtoolbox over HTTPS reverse proxy it will give me silent errors, site keeps loading (error code 301)

Works fine over HTTP reverse proxy.

Any ideas? is something hardcoded so it will try to open every query in http instead of https?

HTTPS
[21/Jul/2023:15:40:43 +0000] - 301 301 - GET https spf.jaska.cc "/operations?domain=jaska.cc&request=a&port=" [Client 192.168.10.100] [Length 357] [Gzip -] [Sent-to 192.168.10.20] "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "https://spf.jaska.cc/"

HTTP
[21/Jul/2023:15:41:27 +0000] - 200 200 - GET http spf.jaska.cc "/operations/?domain=jaska.cc&request=a&port=" [Client 192.168.10.100] [Length 139] [Gzip -] [Sent-to 192.168.10.20] "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "http://spf.jaska.cc/"

E: Nevermind I just had to add header to upgrade the http requests
Content-Security-Policy: upgrade-insecure-requests;

Originally created by @jaska087 on GitHub (Jul 21, 2023). Original GitHub issue: https://github.com/charlesabarnes/SPFtoolbox/issues/64 Hi. Just a weird issue. Serving SPFtoolbox over HTTPS reverse proxy it will give me silent errors, site keeps loading (error code 301) Works fine over HTTP reverse proxy. Any ideas? is something hardcoded so it will try to open every query in http instead of https? HTTPS `[21/Jul/2023:15:40:43 +0000] - 301 301 - GET https spf.jaska.cc "/operations?domain=jaska.cc&request=a&port=" [Client 192.168.10.100] [Length 357] [Gzip -] [Sent-to 192.168.10.20] "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "https://spf.jaska.cc/"` HTTP `[21/Jul/2023:15:41:27 +0000] - 200 200 - GET http spf.jaska.cc "/operations/?domain=jaska.cc&request=a&port=" [Client 192.168.10.100] [Length 139] [Gzip -] [Sent-to 192.168.10.20] "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "http://spf.jaska.cc/"` E: Nevermind I just had to add header to upgrade the http requests Content-Security-Policy: upgrade-insecure-requests;