Global Directory
Global Directory
EXPLORE OUR SITES
London Stock Exchange Group
LSEG Data & Analytics
MyAccount
LSEG Perspectives
London Stock Exchange
FTSE Russell
LCH
Contact Us
Home
TR Internal
How do I route css in StaticContent
shaggyalien
`Css=10.208.113.19-9000.ip.int.next.ci.westlaw.com&CssInternal=10.208.113.19-9000.ip.int.next.ci.westlaw.com`
Should this suffice ? I have tried this but the pages appear without css being applied.
Find more posts tagged with
static-data
refinitiv-internal
Accepted answers
mark.maruska
Yes, that domain name format looks correct, you can test it standalone...
[
http://10.208.113.19-9000.ip.int.next.ci.westlaw.com/Platform/css/v2/document.css](http://10.208.113.19-9000.ip.int.next.ci.westlaw.com/Platform/css/v2/document.css)
If you are using https (SSL), then many times the static content does not load because of an SSL cert issue. To resolve an SSL cert issue like this, you should grab the url for the CSS file that's in the "View Source" content of the web page and request that url directly. This will make the browser prompt with the SSL cert issue and allow you to add an exception -- so the CSS file is displayed. Then reloading your original page should work. Here's the same file using SSL that you can try...
[
https://10.208.113.19-9000.ip.int.next.ci.westlaw.com/Platform/css/v2/document.css](https://10.208.113.19-9000.ip.int.next.ci.westlaw.com/Platform/css/v2/document.css)
All comments
Ryan Morlok
Does the markup rendered by Website include appropriate links to the CSS when you do this? Does firebug show that the browser successfully retrieved the CSS for those links? When running Cobalt Website, I normally have static content on port 81, are you sure you want port 9000?
mark.maruska
Yes, that domain name format looks correct, you can test it standalone...
[
http://10.208.113.19-9000.ip.int.next.ci.westlaw.com/Platform/css/v2/document.css](http://10.208.113.19-9000.ip.int.next.ci.westlaw.com/Platform/css/v2/document.css)
If you are using https (SSL), then many times the static content does not load because of an SSL cert issue. To resolve an SSL cert issue like this, you should grab the url for the CSS file that's in the "View Source" content of the web page and request that url directly. This will make the browser prompt with the SSL cert issue and allow you to add an exception -- so the CSS file is displayed. Then reloading your original page should work. Here's the same file using SSL that you can try...
[
https://10.208.113.19-9000.ip.int.next.ci.westlaw.com/Platform/css/v2/document.css](https://10.208.113.19-9000.ip.int.next.ci.westlaw.com/Platform/css/v2/document.css)
shaggyalien
I guess I should have checked that first. I think the url where StaticContent is looking for Css files is different.
`
https://10.208.113.19-9000.ip.int.next.ci.westlaw.com/css/v2/hover.css`
when it should be
`
https://10.208.113.19-9000.ip.int.next.ci.westlaw.com/Platform/css/v2/hover.css`
shaggyalien
Thanks for the reply, I am aware of this trick. I think for some reason StaticContent is looking for css files in wrong location.
I am running SC on Apache Httpd. Its faster than HFS and I haven't seen any problems until now.
Quick Links
All Forums
Recent Questions
Terms of use
Privacy & Cookie Statement
Cookies settings
Do not sell my info
Whistleblowing
UK Bribery Act
Modern Slavery Act