Re: Re: Oddball port number

Thanks for the reply.  I'm using jetty as a general purpose web server 
hosting a few servlets and static content.
I configured Jetty to listen on port 8081 like this

<Configure class="org.mortbay.jetty.Server">
  <Call name="addListener">
    <Arg>
      <New class="org.mortbay.http.SocketListener">
        <Set name="Port">8081</Set>

...and so on.  I deploy webapps just by copying them to a deployment directory which is
specified as

  <Call name="addWebApplications">
    <Arg></Arg>
    <Arg>/www/webapps/</Arg>
    <Arg>org/mortbay/jetty/servlet/webdefault.xml</Arg>
    <Arg type="boolean">true</Arg>
  </Call>

I deployed pixory just by putting it into /www/webapps.  Unpacked; that is, it's not a
.war file it's just a directory.

I agree it doesn't make sense, I would have expected Pixory to just use the context that
it's called by.  My other servlets don't get very much exercise but I haven't noticed
this problem with them.

Sigh.  And it had been working so well before on port 80.  One day I'll figure it out.



rpu43 wrote:

>Guy,
>
>My explanation (but Joe knows for sure)
>
>I don't understand if you use the embedded Jetty or a Jetty instance
>in which you deploy the War. The behaviour you described is not
>configured in Pixory. Pixory the webapplication is not aware of ports.
>The port you can set in the userinterface sets the port of the
>embedded Jetty server.
>
>Joe said this about it: 
>  
>
>>Pixory doesn't hard code the "web context"
>>(http://hostname:port)-- it should always use the "web
>>context" of the requesting URL. So if your guest
>>arrives at Pixory (via a proxy) with URL
>>http://yourhost, then all of the navigation should be
>>based on that context, and not some other hardcoded
>>context. Of course, if you proxy is _rewriting_ the
>>URLs, then that's a different story. The important
>>thing is the request URL that shows up to the Pixory
>>web application.
>>    
>>
>
>So I assume that it is something of Jetty.
>I have a Pixory instance under Tomcat which runs under port 8080. When
>I use it locally ALL urls are like localhost:8080/bladiebla.
>But when is access my server from the Internet where a router and an
>Apache server lives in front of Tomcat I access it like pics-----.com
>and somewhere along the line translate the port 80 to 8080. Pixory
>still returns urls with the original port 80.
>
>So do you do something portwise with Jetty?
>
>Ronald
>
>--- In [email protected], "guyhillyer" <guy@f...> wrote:
>  
>
>>I moved the servlet container (jetty) that is hosting my pixory webapp
>>from port 80 to port 8081 -- this was because my stupid new Belkin
>>router occupies port 80 for its own admin interface.
>>
>>Now I find that I can get to Pixory's front page at port 8081, but the
>>link for each album on that page lacks the port number in the url.
>>
>>How can I tell Pixory it's on a different port number?
>>
>>My Pixory is at beta.3.11.
>>
>>Thanks
>>
>>  -- Guy
>>    
>>
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>  
>



------------------------ Yahoo! Groups Sponsor --------------------~--> 
Fair play? Video games influencing politics. Click and talk back!
http://us.click.yahoo.com/T8sf5C/tzNLAA/TtwFAA/EGnolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/pixory-beta/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/