Implementation of routing page's additional "Request Headers"
How is the routing page's additional request headers field implemented in Website? It appears that the additional headers you specify will be included in any request to modules issued by Website server side but won't be included in any ajax request to modules. Could this be done?
Tagged:
2
Best Answer
-
James is right about the half baked part. The headers are only added to outgoing server-side calls. Adding them to AJAX calls would probably require including the array of headers in the JavaScript on every page or storing them in a cookie. On top of this, they would need to be hooked into the Cobalt.Net.WebRequest code. If I remember correctly, we left out the AJAX side of it because the people requesting this only needed it on server-side calls and we didn't have the time for the addition to the JavaScript.2
Answers
-
This sounds like a Website feature request (?).0
-
Check with @AdamLemker, looks like he implemented it originally. My guess is that it is only half-baked (no offense to Adam), such that Website will pass those headers on server-side calls but not on AJAX calls. Additionally, the HttpClient infrastructure libraries might need to be updated to support passing these headers along for server-side calls beyond Website (e.g. Document calling DataOrchestrator).2
-
Possibly - wasn't sure what was already implemented when that was added to the routing page. Plus, wanted an understanding of how it does work today.0
-
Thanks for the good info Adam - sounds like if the desire exists for those optional headers to be passed along on ajax calls we'd need to pursue that in Website/Static Content0
-
Schu: Should be pretty easy to implement the AJAX header passing. My bigger concern would be if the HttpClient libs are going to pass them along... my guess is that it would not, since it can't really anticipate what custom headers you'll be setting/overriding. That would probably have to be done manually...?0
-
I heard a rumor (unconfirmed) that the infrastructure HttpClients will honor headers with certain prefixes (e.g. x-cobalt-product...) so it _may_ work.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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛