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 email@example.com -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).
- Stepping into Science
- CORSAIR's Carbide Air 740
- A Better Raspberry Pi Streaming Solution
- Qu’est-ce qu’on a fait au Bon Dieu ? Télécharger Le Film Complet Gratuit
- Linux Journal December 2016
- Tyson Foods Honored as SUSE Customer of the Year
- FutureVault Inc.'s FutureVault
- Radio Free Linux
- The Tiny Internet Project, Part II
- Message for You, Sir!