Trouble routing Static Content locally -- GET failures

Over the last week I've started having considerable troubles when trying to route to local Static Content. The routing page is set up the same way I always set it up (modifying the JavaScript and JavaScriptInternal fields to point to my Big IP address). The problem comes after signing on with One Pass. I'm getting failures for the GET requests of various Core JS files such as Cobalt.Hub.js and Cobalt.Browser.SessionStorage.js. There are consistently 5-10 failures and they're attempting to be fetched from https://1.next.demo.westlaw.com/.

This happens sporadically and seems to have no correlation to anything I'm doing. Any ideas?

Find more posts tagged with

static-data

refinitiv-internal

Accepted answers

Kyle Reich

This ultimately turned out to be due to incorrect routing parameters. I'm not sure why I used to be able to get away with it, but something changed towards the end of November and it's much more sensitive/strict now.

Mark Maruska provided the following feedback which took care of my problems (making sure the route matched the environment (CI or DEMO as it were):

Hi all, it is my understanding that in general, routing static content locally should use the ip hostname with the addition of the "sc-" prefix. Additionally, the ip hostname should match the environment that is being used -- that is, ci for ci, demo for demo, etc. Thanks! ~ Mark

Example for demo on the routing page (version is live now)...

JavaScript: sc-10.204.78.78-9522.ip.next.demo.westlaw.com/StaticContent_26.0.37
JavaScriptInternal: sc-10.204.78.78-9522.ip.int.next.demo.westlaw.com/StaticContent_26.0.37

Routing page prefilled...

https://1.next.demo.westlaw.com/routing?JavaScript=sc-10.204.78.78-9522.ip.next.demo.westlaw.com/StaticContent_26.0.37&JavaScriptInternal=sc-10.204.78.78-9522.ip.int.next.demo.westlaw.com/StaticContent_26.0.37

And yes, you would need to add https cert exceptions in the browser when using https.

All comments

Joel Peterson

Kyle,
Are you routing to -.ip.next.ci.westlaw.com when you are on Demo? That used to work fine, but there seems to have been some change recently that is affecting that routing strategy. Try routing to ip.next.demo.westlaw.com and see if that works for you.

Kyle Reich

This didn't work. I get a ton of errors in the console when I use your suggestion. Also, what would cause anything to be directed to your machine in this case?

Joel Peterson

Those errors are probably SSL cert warnings. If you use Chrome and have the dev tools open to the network tab, you can right click on one of the failed script loads and open in a new tab. It will tell you that it is unsafe, but if you click to continue then it will remember the exception for the rest of your browser session. You can then refresh your original page and it should work.

BigIP sees the URL and forwards the request to the ip and port specified instead of sending it on to the WLN server.

Kyle Reich

I appreciate your help thus far. The errors aren't HTTP errors, they're JS errors. Lots of Uncaught SyntaxError and Uncaught Reference Error exceptions.

Uncaught SyntaxError: Unexpected token <
Uncaught ReferenceError: Cobalt is not defined

Kyle Reich

EXPLORE OUR SITES