Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Jetty/Howto/Configure Virtual Hosts"

< Jetty‎ | Howto
(New page: {{Jetty Howto | introduction = A virtual host is an alternative name, registered in DNS, for an IP address. A single IP address may have many such alternative names. Multi-homed hosts, t...)
 
Line 175: Line 175:
 
* http://www.other.net:8080/
 
* http://www.other.net:8080/
 
* http://www.other.org:8080/
 
* http://www.other.org:8080/
 
</div>Labels parameters    <div id="labels-section" class="pageSection"><div id="default-labels-header" class="section-header">
 
 
==Labels==
 
 
</div><div class="labels-editor"><div id="labelsList"></div><span id="errorSpan" class="errorMessage error"></span><div id="labelInputSpan" class="labels-input"><div id="labelOperationErrorContainer" class="hidden"><span class="error"><span id="labelOperationErrorMessage" class="errorMessage"></span></span></div><div class="caption">Enter labels to add to this page:</div><div id="label-input-fields">  </div><div id="waitImageAndStatus">[[Image:wait.gif|Please wait]]  <span id="labelOperationStatus" class="smalltext"></span></div><div id="labelsAutocompleteList" class="aui-dd-parent"></div><div class="labels-tip"><div id="suggestedLabelsSpan"></div> Looking for a label? Just start typing. </div></div></div></div> <div id="comments-section" class="pageSection"><div class="section-header ">
 
 
==Comments (1)==
 
 
* [/display/JETTY/Virtual+hosts?showComments=false#comments Hide Comments] [/display/JETTY/Virtual+hosts?showComments=true#comments Show Comments]
 
* [# Collapse All] <span id="collapse-wait" class="hidden">Collapsing…</span> <span id="expand-wait" class="hidden">Expanding…</span> [# Expand All]
 
  
</div>
 
 
# <div id="comment-32735320" class="comment  ">[/display/~mboehm [[Image:default.gif]]]Dec 01, 2007<div class="comment-header comment-toggle">====[/display/~mboehm Maximilian Böhm] says:====<span class="excerpt">Hi, i'm configuring jetty with some helper-methods. One problem is, that i have...</span></div><div class="comment-body"><div class="comment-content wiki-content">Hi,i'm configuring jetty with some helper-methods. One problem is, that i have to restart jetty to overtake the changes i've done with context.setVirtualHosts. Is there a mistake by me or doesn't it work else?Thanks in advanceGreetzPS.: Here the code:<div class="code panel" style="border-width: 1px"><div class="codeContent panelContent">    <span class="code-keyword">public</span> void addVirtualHost(Context context, <span class="code-object">String</span> sDomain) <span class="code-keyword">throws</span> Exception{
 
      <span class="code-object">int</span> nOldVHosts = context.getVirtualHosts().length+1;
 
      <span class="code-object">String</span>[] nNewVHosts = <span class="code-keyword">new</span> <span class="code-object">String</span>[nOldVHosts];
 
      <span class="code-keyword">for</span> (<span class="code-object">int</span> i = 0; i < context.getVirtualHosts().length; i++) {
 
          nNewVHosts[i] = context.getVirtualHosts()[i];
 
      }
 
      nNewVHosts[nOldVHosts-1] = sDomain;
 
     
 
      context.setVirtualHosts(nNewVHosts);
 
     
 
      server.stop();
 
      server.start();
 
    }
 
   
 
 
</div>
 
</div>
 
| prereqs = (optional)
 
| prereqs = (optional)

Revision as of 18:39, 8 July 2010



Introduction

A virtual host is an alternative name, registered in DNS, for an IP address. A single IP address may have many such alternative names.

Multi-homed hosts, that is machines with more than one network interface, may have a different name for each IP address. This is also refered to as "virtual hosting".

Essentially, "virtual hosting" concerns the resolution of a DNS registered name to an IP address - many names may resolve to the same IP address, and 1 or more IP addresses may reside on the same physical machine.

Jetty users often want to configure their web applications taking into account these different virtual hosts. Frequently, a machine with a single IP address will have different DNS resolvable names associated with it, and a webapp deployed on it must be reachable from all of the alternative names.

Other possibilities are to serve different web applications from different virtual hosts.

Let's examine these possibilities.

Configuration of virtual hosts

When configuring a web application, you can supply a list of IP addresses and names at which the web application will be reachable. Suppose we have a machine with these IP addresses and DNS resolvable names:

  • 333.444.555.666
  • 127.0.0.1
  • www.blah.com
  • www.blah.net
  • www.blah.org

Suppose we have a webapp, xxx.war that we want to be served from all of the above names and addresses. Then we would configure the webapp like so:


    <Configure class="org.mortbay.jetty.webapp.WebAppContext">
      <Set name="contextPath">/xxx</Set>
      <Set name="war"><SystemProperty name="jetty.home"/>/webapps/xxx.war</Set>
      <Set name="virtualHosts">
        <Array type="java.lang.String">
          <Item>333.444.555.666</Item>
          <Item>127.0.0.1</Item>
          <Item>www.blah.com</Item>
          <Item>www.blah.net</Item>
          <Item>www.blah.org</Item>
        </Array>
      </Set>
    </Configure>

Assuming we'd configured a connector listening on port 8080, then webapp xxx.war would be available at all of the following addresses:

Configuring different webapps for different virtual hosts

This is accomplished simply by supplying a different list of virtual hosts for each webapp. For example, suppose our imaginary machine has these DNS names and IP addresses:

  • 333.444.555.666
  • 127.0.0.1
  • www.blah.com
  • www.blah.net
  • www.blah.org
  • 777.888.888.111
  • www.other.com
  • www.other.net
  • www.other.org

Suppose also we have another webapp, zzz.war. We want xxx.war to be deployed as above, and zzz.war to be deployed only from 777.888.888.111, www.other.com, www.other.net and www.other.org:


    
    <Configure class="org.mortbay.jetty.webapp.WebAppContext">
      <Set name="contextPath">/xxx</Set>
      <Set name="war"><SystemProperty name="jetty.home"/>/webapps/xxx.war</Set>
      <Set name="virtualHosts">
        <Array type="java.lang.String">
          <Item>333.444.555.666</Item>
          <Item>127.0.0.1</Item>
          <Item>www.blah.com</Item>
          <Item>www.blah.net</Item>
          <Item>www.blah.org</Item>
        </Array>
      </Set>
    </Configure>


    
    <Configure class="org.mortbay.jetty.webapp.WebAppContext">
      <Set name="contextPath">/zzz</Set>
      <Set name="war"><SystemProperty name="jetty.home"/>/webapps/zzz.war</Set>
      <Set name="virtualHosts">
        <Array type="java.lang.String">
          <Item>777.888.888.111</Item>
          <Item>www.other.com</Item>
          <Item>www.other.net</Item>
          <Item>www.other.org</Item>
        </Array>
      </Set>
    </Configure>

Webapp xxx.war is still available at:

But now webapp zzz.war is available at:

Configuring different webapps for different virtual hosts, but at the same context path

In our example above, we have made webapp zzz.war avilable not only at a certain set of virtual hosts, but also at the context path /zzz, whilst our other webapp is available at both a different set of virtual hosts, and at a different context path. What happens if we want them at the same context path, but still at different sets of virtual hosts?

Very simply, we just supply the same context path for each webapp, leaving the disjoint set of virtual host definitions as before:


    <Configure class="org.mortbay.jetty.webapp.WebAppContext">
      <Set name="war"><SystemProperty name="jetty.home"/>/webapps/xxx.war</Set>
      <Set name="contextPath">/</Set>
      <Set name="virtualHosts">
        <Array type="java.lang.String">
          <Item>333.444.555.666</Item>
          <Item>127.0.0.1</Item>
          <Item>www.blah.com</Item>
          <Item>www.blah.net</Item>
          <Item>www.blah.org</Item>
        </Array>
      </Set>
    </Configure>


    <Configure class="org.mortbay.jetty.webapp.WebAppContext">
      <Set name="war"><SystemProperty name="jetty.home"/>/webapps/zzz.war</Set>
      <Set name="contextPath">/</Set>
      <Set name="virtualHosts">
        <Array type="java.lang.String">
          <Item>777.888.888.111</Item>
          <Item>www.other.com</Item>
          <Item>www.other.net</Item>
          <Item>www.other.org</Item>
        </Array>
      </Set>
    </Configure>

Now, webapp xxx.war is available at:

and webapp zzz.war is available at:

</div>

Prerequisites

(optional)

Steps

(optional)

Tips, Hints, and Warnings

(optional)

Examples

(optional)

Snippets and Screenshots

(optional) - for chunks of code that are too big to go into the Steps section, or screenshots

Additional Resources

(optional) - links, additional references

Back to the top