Unsightly Tomcat port number issue.
I've been trying to figure out why Mozblog will not work with Roller's Blogger API implementation. I haven't had much luck, but I have again come across an irritating little issue with the Servlet API request.getRequestURL() method. I'm calling on the blog support line for advice.
Tomcat/Servlet experts, what do you make of this comment from Roller's RollerContext.getContextUrl() method?
// If you are running Roller behind a foreground server, // then your Servlet engine may be operating on a different // port than your forground server. For example, I run Roller // on a Tomcat background server that operates behind an // Apache foreground server. My Apache server is on port 80, // but my Tomcat server is on port 1003. // // If this is the case, then request.getRequestURL() may // return a URL that is valid but that includes an unsightly // and unnecessary port number that you would rather not // include in weblog permalink. In other cases (e.g. you are // running a standalone Tomcat instance on port 8080) the port // number is essential. // // To deal with this the Roller getContextUrl() method uses // a configuration parameter to determine if it should include // a port number. It calls request.getRequestURL(), parses apart // the result, and builds a context URL suitable for use in a // permalink with or without a port number.Is that clear? Is there an easier way to deal with this issue?
Dave Johnson
in Java
• 🕒 05:46PM Dec 29, 2002
Tags:
Java
Posted by Matt Raible on December 30, 2002 at 04:16 AM EST #
Posted by John W. Mendes on December 30, 2002 at 05:32 PM EST #
Posted by Rickard Ãberg on December 31, 2002 at 06:44 AM EST #
Posted by Dave Johnson on May 07, 2003 at 12:36 AM EDT #