Changes for page Tomcat Installation

Last modified by Thomas Mortagne on 2023/12/01

<
From version < 50.2 >
edited by Vincent Massol
on 2019/01/28
To version < 51.1 >
edited by Paul Libbrecht
on 2019/05/24
>
Change comment: Enriching with a paragraph about combining proxy and tunnel

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.VincentMassol
1 +XWiki.polx
Content
... ... @@ -248,6 +248,15 @@
248 248  
249 249  For more background on this config, see the discussion on this ticket: [[XWIKI-13963>>http://jira.xwiki.org/browse/XWIKI-13963||rel="__blank"]].
250 250  
251 +=== Proxying and tunnels ===
252 +
253 +This proxy methods brings remote connections to local connection. This is complementary to SSH-tunneling which is easily done on port 8080 and can be used to test development servers.
254 +
255 +For example, if you are running an XWiki on port 80 on your laptop while running the NGinx (or Apache) on a server where it is accessible as ##{{{https://wiki.yourdomain.com}}}##, you can make your XWiki acessible with this URL:
256 +
257 +* First make sure that the port 8080 is not in use: You can proof this with ##{{{ssh server wget -O - https://127.0.0.1:8080/}}}## which should display the error message //Connection refused//. If not, something is running there and it should be stopped.
258 +* You can then create the tunnel with the following ##ssh -R8080:127.0.0.1:8080 server##. This tells the server that incoming ("R"emote) connections on port 8080 on the server are to be tunnelled to the local (laptop) port 8080. This method has the advantage that the laptop (typically using a dynamic address) invokes the SSH where as a proxy configured on the server to proxy to the laptop would need to know the address of the laptop.
259 +
251 251  == Configuring tomcat for https ==
252 252  
253 253  Although allowing users to directly connect to tomcat is not recommended, for a variety of reasons it may be desirable to configure tomcat to serve pages over an https connection.

Get Connected