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 oehmsmith@xx.xx.65.14 -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).

Feedback appreciated!



White Paper
Linux Management with Red Hat Satellite: Measuring Business Impact and ROI

Linux has become a key foundation for supporting today's rapidly growing IT environments. Linux is being used to deploy business applications and databases, trading on its reputation as a low-cost operating environment. For many IT organizations, Linux is a mainstay for deploying Web servers and has evolved from handling basic file, print, and utility workloads to running mission-critical applications and databases, physically, virtually, and in the cloud. As Linux grows in importance in terms of value to the business, managing Linux environments to high standards of service quality — availability, security, and performance — becomes an essential requirement for business success.

Learn More

Sponsored by Red Hat

White Paper
Private PaaS for the Agile Enterprise

If you already use virtualized infrastructure, you are well on your way to leveraging the power of the cloud. Virtualization offers the promise of limitless resources, but how do you manage that scalability when your DevOps team doesn’t scale? In today’s hypercompetitive markets, fast results can make a difference between leading the pack vs. obsolescence. Organizations need more benefits from cloud computing than just raw resources. They need agility, flexibility, convenience, ROI, and control.

Stackato private Platform-as-a-Service technology from ActiveState extends your private cloud infrastructure by creating a private PaaS to provide on-demand availability, flexibility, control, and ultimately, faster time-to-market for your enterprise.

Learn More

Sponsored by ActiveState