When you want to play around with the proxy and see if the SSR cache is working properly, you'll want to use the
WRDebug messages on the bottom of your screen when you are on the a
Look for this on the bottom of your screen.
WRDebug is only be visible on your webrender.io subdomain and can be disabled
|What it says||What it means||Action taken|
|A user (client that supports JS) hit the page, but missed the cache - the proxy will grab the file from your origin and serve it, but SSR will not be necessary||It will be indexed soon, you will see it as a miss in your logs|
|A crawler (a bot or client that does not support JS) hit the page but it was not in cache, we generated it on the fly to make sure it is readable, unless it supported JS, in which case it will be fetched from origin.||It will be indexed soon, you will see it as a miss in your logs|
|A user hit the SSR cache, which means server side rendering worked (no page flickers etc) and JS is enabled since we want the page to remain usable for the user to click around||None, you will see it as a hit in your logs|
|A crawler hit the SSR cache and was served a page with JS disabled to prevent double-rendering and loading speed as it won't click around anyways||None, you will see it as a hit in your logs|
For any other debugging, you'll want to use logs and stats in the dashboard, or use Webhooks
Logs and stats are available in the dashboard. If those don't solve your problem, we recommend setting up a Webhook into Honeycomb or your own domain so you can debug every request individually.
These are visible in the dashboard in the Logs tab
|Key||Description||how to see|
|timestamp of the request||in the table|
|Whether the request is static||indicated by the page icon|
|The URL of the request||in the table|
|2-letter ISO code of the request country||in the table|
|The Webrender-Identified platform of the request||in the table|
|Whether it was a hit or a miss||indicated via eye icon|
Use the path-specific disable key to disable debug on certain paths. Or all of them if you just don't want to see them.
If a path is getting spammed by certain user agents, you can disable them on certain paths.
Note: we generate your stats from your logs, so disabling logs will disable stats.