Project

General

Profile

Actions
Copy link

Bug #2264

closed

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

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

Added by Nicolas CHARLES over 13 years ago. Updated about 13 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)

Related to Rudder - Bug #2282: One can not omit the configuration of a base URL in rudder propertiesReleasedVincent MEMBRÉActions

Updated by Nicolas CHARLES over 13 years ago Actions
Copy link
 #1

<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

Updated by Matthieu CERDA over 13 years ago Actions
Copy link
 #2

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.

Updated by Matthieu CERDA over 13 years ago Actions
Copy link
 #3

  • Status changed from New to Discussion

Updated by Matthieu CERDA over 13 years ago Actions
Copy link
 #4

OK, it failed. I opened another issue to track this at #2282

Updated by Jonathan CLARKE over 13 years ago Actions
Copy link
 #5

  • Target version changed from 2.4.0~alpha6 to 2.4.0~alpha7

Updated by Jonathan CLARKE over 13 years ago Actions
Copy link
 #6

  • Target version changed from 2.4.0~alpha7 to 2.3.8

Updated by Jonathan CLARKE over 13 years ago Actions
Copy link
 #7

  • Target version changed from 2.3.8 to 2.3.9

Updated by Jonathan CLARKE about 13 years ago Actions
Copy link
 #8

  • Category changed from 11 to Web - UI & UX

Updated by Jonathan CLARKE about 13 years ago Actions
Copy link
 #9

  • Status changed from Discussion to Rejected

This should be fixed by #2282, but only for Rudder 2.4.x. This won't be fixed in Rudder 2.3.x.

Actions
Copy link

Also available in: PDF Atom