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).
Webinar: 8 Signs You’re Beyond Cron
11am CDT, April 29th
Join Linux Journal and Pat Cameron, Director of Automation Technology at HelpSystems, as they discuss the eight primary advantages of moving beyond cron job scheduling. In this webinar, you’ll learn about integrating cron with an enterprise scheduler.Join us!
- The Yorick Programming Language
- Interview with Linus, the Author of Linux
- Tips for Optimizing Linux Memory Usage
- Tutorial: Emacs for Programmers
- Boot with GRUB
- What's Intel up to with VIIV?
- Hack and / - When Disaster Strikes: Attack of the rm Command
- Bash Arrays
- Blu-ray Encryption—Why Most People Pirate Movies
- Girls and Software