Bug #2264: When using the webapp through port forwarding, the css are not loaded - Rudder - Issue Tracker

Actions

Copy link

Bug #2264

closed

When using the webapp through port forwarding, the css are not loaded

Added by Nicolas CHARLES almost 13 years ago. Updated about 12 years ago.

Status:

Rejected

Priority:

N/A

Assignee:

Category:

Web - UI & UX

Target version:

2.3.9

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

As we've been told :
I forwarded port 9000 of my PC to port 80 inside the vm, but then I had no css - I set the FQDN to localhost, so the css links are http://localhost/something.css - wouldn't it be better to use /something.css instead?

We need to find a solution for this (look at Apache or the code, or both ?)

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nicolas CHARLES almost 13 years ago

<Ronny1> it was not a big problem because I changed the forwarding so that it is pc:80 -> vm:80 instead of pc:9000 -> vm:80 and then it worked

Actions

Copy link

Updated by Matthieu CERDA almost 13 years ago

As far as I can tell, this configuration property might help :

##
# Application information
##
#define that property if you are behind a proxy
#or anything that make the URL served by the
#servlet container be different than the public one
#note: if defined, must not end with /
#let blank to use default value
base.url=http://foo.bar.baz/rudder

As seen in the explicative comment, one might maybe comment it so you do not have an enforced FQDN for the CSS. I'll try this.

Actions

Copy link