Debugging proxies can be incredibly frustrating, and over the last year, we've developed tools to help your customers with that.
First, we've introduced our live activity overview and a comprehensive error code system that can provide more than enough information to get your proxies back on track. Now, we've gone a step further and overhauled our error codes to be even more informative.
We return these error codes to you in headers returned during the proxy handshake. No more cross-referencing with the live activity overview.
Here's an example, using a request with a target on our block list:
```
❯ curl -x http://USER:[email protected]:61234 http://super-bad-domain.com -v
** [READACTED FOR BREVITY] **
< HTTP/1.1 502 Bad Gateway
< x-byteful-warp-enabled: false
< x-byteful-status-code: 3162
< x-byteful-request-id: 37136d7f-b61d-4169-b885-3ee469b45e98
< transfer-encoding: chunked
<
You are accessing a restricted target. Please contact [email protected] if you believe this is incorrect.
```The `x-byteful-request-id` and `x-byteful-status-code` headers are useful here. The request ID can be used to correlate a request with the live activity overview on the dashboard. The status-code can be cross-referenced against our documentation.
If you look the `3162` code up you will see it matches the `316x` category of errors:
In your use cases, you'll find that our errors comprehensively cover every configuration issue you could encounter with your proxy. Combined with our live activity overview, we believe we have best-in-class observability into why your requests have failed, allowing you to resolve problems more quickly and with less stress than with any other provider.
We hope these changes improve the experience of using our proxies for our users, and, as always, we're happy to hear from our customers about any other changes we could make to improve their workflows.
