ssh tunnel to http which redirects to https failure
Gidday LJ and LJ fans,
I'm a long time dabbler in the 'nix black arts but only recently got serious about it.
I run tomcat at home for, amongst other things, my wiki. I set it up with fairly serious security to require users to login, and it also forces redirection to https for all read/write.
I've just setup a ssh tunnel so I can access it (thank to Linux Journal's help).
ssh -T -N -L 3210:localhost:8080 firstname.lastname@example.org -oPort=13213
So this ssh' to port 13213 on my server and it redirects to port 8080. That's how i understand it and that part seems to work.
The tomcat and its included examples, documentation and other webapps come up fine. But when I hit my wiki the security redirects to:
(Mmmm, I'm not sure why it isn't https://kanga.local:8443. But that is not an issue at the moment).
And kanga.local is of course local to my home network.
I tried setting the tunnel directly to :8443 (https) but when I go to access Tomcat what's returned is a binary (encrypted) file.
As I'm new to this I'm hoping somebody more wise than I in this area can tell me what I can do to get around this (apart from killing the security policy I've setup on my wiki).
Practical books for the most technical people on the planet. Newly available books include:
- Agile Product Development by Ted Schmidt
- Improve Business Processes with an Enterprise Job Scheduler by Mike Diehl
- Finding Your Way: Mapping Your Network to Improve Manageability by Bill Childers
- DIY Commerce Site by Reven Lerner
Plus many more.
- Happy GPL Birthday VLC!
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- Handheld Emulation: Achievement Unlocked!
- Unikernels, Docker, and Why You Should Care
- Giving Silos Their Due
- Controversy at the Linux Foundation
- Don't Burn Your Android Yet
- Firefox OS
- diff -u: What's New in Kernel Development