You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due fact we cannot publish application_id paramter in release application, we have to use our proxy. Also we perform caching on this proxy service to not exceed rate-limiting. Clients are also rate-limited in case they start just spamming us.
All calls which you are now doing to the Wargaming API directly must be rewritten to use this proxy. Instead of using the application_id query parameter you will use Authorization: JwtTokenHere style header authentication. Please also provide required other headers like X-Game and X-Region.
Please see full logic graph bellow.
CORS
Proxy applies CORS rules. CORS is limited currently only to production site usage.
Header Tokens
You can select game and region with HTTP headers.
Region is always mandatory, but if API call includes
game as first path query parameter, will that be used.
For example: api.xxx.eu/wot/account/list will return wot as it is first path argument.
Available tokens are following:
Header
Possible Values
Description
X-Region
eu,na,ru,asia
Which region API server we should use.
X-Game
wot,wows,wowp
Which game API server we should use.
Other
URL to the proxy is not public. Please ask discord #developers to get link to it from @NikoGrano.
Logic
Proxy implementation logic is following
The text was updated successfully, but these errors were encountered:
…uthentication + Implement premature code for Socket.io (#196)
* WIP
* #193 - Migrate from WG API to Proxy + update Room state
* Remove console logs for authentication
…uthentication + Implement premature code for Socket.io (#196)
* WIP
* #193 - Migrate from WG API to Proxy + update Room state
* Remove console logs for authentication
Wargaming API Proxy
Due fact we cannot publish
application_id
paramter in release application, we have to use our proxy. Also we perform caching on this proxy service to not exceed rate-limiting. Clients are also rate-limited in case they start just spamming us.All calls which you are now doing to the Wargaming API directly must be rewritten to use this proxy. Instead of using the
application_id
query parameter you will useAuthorization: JwtTokenHere
style header authentication. Please also provide required other headers likeX-Game
andX-Region
.Please see full logic graph bellow.
CORS
Proxy applies CORS rules. CORS is limited currently only to production site usage.
Header Tokens
You can select game and region with HTTP headers.
Region is always mandatory, but if API call includes
game as first path query parameter, will that be used.
For example:
api.xxx.eu/wot/account/list
will return wot as it is first path argument.Available tokens are following:
Other
URL to the proxy is not public. Please ask discord #developers to get link to it from @NikoGrano.
Logic
Proxy implementation logic is following
The text was updated successfully, but these errors were encountered: