Are you setting the absolute url in the admin settings page?
Roller will attempt to automatically determine the absolute url to the
instance on it's own if you don't manually specify it, so it's possible
that it is thinking that the instance is on port 8080.
If you are talking about redirects and other things not forming the
right urls then I think you need to look at the tomcat config for you
ajp connector. I believe there is a setting in there which lets you
tell tomcat that the real port of the service is something other than
the port the appserver is running, I think it may be called "proxyPort"
or something like that.
-- Allen
Sloan Bowman wrote:
Well that didn't work. It does get rid of the port 8080 but it just tacks on
the url at the end again. For example www.domain.com/www.domain.com/link. Any
ideas?
Thanks,
Sloan
-----Original Message-----
From: "mohamed felfel" <[EMAIL PROTECTED]>
Date: Fri, 18 May 2007 15:03:03
To:[email protected]
Subject: Re: Roller and mod_jk
You have to go to your "sever administration" section, and change the home
url accordingly. i ThInK!!!!
On 5/18/07, Sloan Bowman <[EMAIL PROTECTED]> wrote:
Guys,
I'm just getting starting with rollerweblogger and wanted to know
if
you guys have run across this problem. I'm setting up a new template
based on the default theme and everything works just fine. After I
got it all working properly I configured mod_jk on the apache server
to forward all request to tomcat which it does perfectly. The problem
is the links such as comment, read more etc.. on the blog entries
still points to the www.domainname.com:8080 event though I'm runnning
it over port 80. Is this a setting inside of rollerweblogger? Has
anybody else run up against this? Thanks for the help.
Regards,
Sloan
