Strategies for debugging StaticContent in QED with SSL?
Hello,
I'm wondering if anyone has any experience routing a deployed QED Website instance to a local StaticContent instance? The trouble I'm having is that in QED everything is SSL/HTTPS, so if I use the routing page to route static content to my IP/port combo (ex. `10.123.1.1:81`), the root URL ends up being `https://10.123.1.1:81`, which won't work locally. The other approach I tried was to use the following URL in the routing page: `
10.208.104.248-81.ip.next.qed.westlaw.com` I would expect the URL above to act as a proxy between a server that has working SSL and my local StaticContent server which doesn't have SSL. This seems to work, but every file is coming back as an empty file. So, has anyone found a working approach to routing QED to local static content? Any help is much appreciated!
I'm wondering if anyone has any experience routing a deployed QED Website instance to a local StaticContent instance? The trouble I'm having is that in QED everything is SSL/HTTPS, so if I use the routing page to route static content to my IP/port combo (ex. `10.123.1.1:81`), the root URL ends up being `https://10.123.1.1:81`, which won't work locally. The other approach I tried was to use the following URL in the routing page: `
10.208.104.248-81.ip.next.qed.westlaw.com` I would expect the URL above to act as a proxy between a server that has working SSL and my local StaticContent server which doesn't have SSL. This seems to work, but every file is coming back as an empty file. So, has anyone found a working approach to routing QED to local static content? Any help is much appreciated!
Tagged:
2
Best Answer
-
Route locally for static content from QED. 1. Instead of using just the ip address `10.123.1.1:81`, make sure you're using the QED domain name like `
10.123.1.1-81.ip.next.qed.westlaw.com`. 2. In many cases, the SSL certs are not quite right for internal environments. Please look to
add SSL cert exceptions for all static content locations to ensure the files can be loaded. I don't think there is an explicit SSL cert error for static content, so that may appear to be getting blank files. One way to do this is by navigating to
https/[ipaddress]-[port].
ip.next.qed.westlaw.com/Platform/js/v1/Core/Cobalt.Loader.js in your browser of choice. You will get a certificate error... add an exception for this certificate. We use self-signed certs. 4. Navigate to
next.qed.westlaw.com/routing, then replace the “JavaScript” and “JavaScriptInternal” values with [ipaddress]-[port].
ip.next.qed.westlaw.com and signon. Note, in some scenarios, it may help to add the "sc-" prefix on the domain name so the iRules can help route more directly. For example,
sc-[ipaddress]-[port].
ip.next.qed.westlaw.com2
Answers
-
Thanks Mark! I was using the wrong proxy URL (`qed` instead of `ci`), and didn't have my SSL exceptions entered.0
-
-
Sorry, the QED domain names should work (like
10.123.1.1-81.ip.next.qed.westlaw.com
). I know there have been issues with the routing for the QED domain names, so if they're not working, then try using the CI domain names.0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛