WebP Cloud now supports custom origin fetch headers

In a previous article titled “WebP Cloud currently supports setting the User-Agent for fetching resources from the origin server on image CDNs, configuring CORS headers, and implementing Referer restrictions.,” we introduced support for setting the origin User-Agent (UA). Users can specify a specific origin UA and configure the origin server to respond only to that UA, achieving a functionality similar to a Pre-shared Key, thereby reducing the possibility of CDN bypassing.

Recently, during discussions with our clients, we discovered a scenario in practical situations where domains and SSL certificates are shared among multiple origin servers, but differentiating them through additional headers. For instance, there could be a unified endpoint named https://global-entrance.some-paas.cloud, which can respond to different backend services based on the X-Forwarded-Host header, as illustrated below:

With customizable origin headers, we can now:

• Access different backend services through the same entrance endpoint using different headers
• Configure headers to access origin services with Authorization
• A/B testing: serving different content based on different headers from the same origin site
• …

Dashboard

Users of the Dashboard can now directly see this feature on the Dashboard!

API

Users utilizing the API can find the method for creating headers at API Reference | WebP Cloud Services Docs.

As with all new features we introduce, WebP Cloud believes in providing equal access to all users. Therefore, whether you are a paid user or a free user, this new feature is now available to you!