Contact
How to report an error in a ZigProxy page, suggest a topic, or tell us about proxy behaviour that differs on the version you are running.
Corrections#
The most valuable message you can send is a correction. Include:
- The page URL.
- The exact sentence or table cell that is wrong.
- What contradicts it: an RFC section, a documentation page, a source file, or a reproducible observation.
- The software version. Proxy behaviour is version dependent, and the answer is often that the page is right for one release and wrong for another, which means the page needs to say so.
Write to corrections@zigproxy.com.
Everything substantive gets logged on the corrections page.
Topic requests#
If there is a proxy question you keep having to re-derive, tell us. Requests that describe a concrete failure ("we could not work out why X returns 502 only under load") are more useful than a topic title, because the failure is what the page needs to resolve.
Write to editorial@zigproxy.com.
What we cannot help with#
- Debugging your specific production incident. This is a reference site, not a support desk. The proxy debugging playbook is the method we would use ourselves.
- Recommending or reselling commercial proxy services. Out of scope, as explained on the about page.
- Circumvention, scraping evasion or attacks on systems you do not operate. These will not be answered.
Vendors#
Corrections about your own product are welcome and are treated exactly like any other correction: verified against primary sources and published if right. Vendors do not get review over content before publication, and no placement in any comparison is for sale.