Re: URL in Email notify missing port information after migration b19 -> b20

We had a similar problem after the upgrade, but ended up just modifying 
our Apache configuration to forward the URLs to the proper port:

# Scarab requests on 80 should go to 8080
RewriteRule ^/scarab/issues/(.*)$ http://ourserver:8080/scarab/issues/$1 [L]

Not the best solution, but time was of the essence.

Brett

On 3/20/2008 5:40 AM, [email protected] wrote:
> Hi All,
> 
> we are facing a problem with URLs in issue change notification emails.
> After we upgraded an installation from b19 to b20 the URLs do not contain
> the http port anymore.
> 
> Before:
> http://scarab.host.lan:48080/scarab/issues/id/ABC123
> 
> After:
> http://scarab.host.lan/scarab/issues/id/ABC123
> 
> We configured the "scarab.http.port" property at build time to be 48080,
> and this value is also present in the current runtime config. After poking
> around a bit I found that a database table named SCARAB_GLOBAL_PARAMETER
> also holds that value. However, in our current installation the value in
> the table is "@SCARAB.HTTP.PORT@". When I manually changed this to 48080
> the port wasn't included in the URL either. But I admit that I didn't
> restart Scarab nor the Tomcat after I did that change.
> 
> Btw. there exists a migration SQL that was created during the build that
> wrote the "@SCARAB.HTTP.PORT@" to the table.
> 
> Any suggestions on how to get that port back into the URL?
> 
> Any help appreciated, regards
> Torsten