WebForge Toolkit 1.2.3
Support
Contact the contributors, report reproducible defects, and find quick resolutions for common browser-extension limitations.
Contact the contributors
Kumar Kartikeya Priyadarshi
Raghavendra Rai
When requesting support, do not email passwords, tokens, private keys, cookies, HAR files, or production response bodies. Provide sanitized reproduction steps instead.
Report an issue
Use the public GitHub issue tracker for reproducible defects and feature requests.
Include Chrome version, WebForge version, selected tool, expected behavior, actual behavior, and sanitized steps. Remove authentication information and sensitive page content before attaching screenshots or exports.
Common troubleshooting
| Problem | Likely cause | Action |
|---|---|---|
| No response body | The resource is not page Fetch/XHR, was loaded before monitoring, or is binary/opaque. | Enable Monitor before reload and use Chrome DevTools for browser-owned resources. |
| Restricted page | Chrome blocks extension scripting on browser-owned pages. | Open a normal HTTP/HTTPS page. |
| API request fails | CORS, TLS, authentication, VPN, or endpoint policy. | Check endpoint logs, certificate trust, headers, and CORS. |
| MQTT/STOMP cannot connect | The broker exposes only a native TCP protocol. | Use a documented WS/WSS MQTT or Web STOMP endpoint. |
| Link check reports Failed | The target rejects extension-origin HEAD/GET or requires authentication. | Verify by normal navigation before treating it as broken. |
See the complete Help Center troubleshooting guide for more examples.
Delete locally stored data
- Use Clear in Network Inspector to remove captured request records.
- Delete saved MQTT, Elasticsearch, or HTTP profiles in Client Utilities.
- Remove saved collections from Request Collections.
- Uninstall WebForge Toolkit from
chrome://extensionsto remove all remaining extension-local storage.
Chrome Web Store reviewer notes
Core formatter, converter, timestamp, HAR, and generator features do not require credentials. Page-aware features require a normal webpage tab. Client tools contact only endpoints entered by the reviewer. MQTT, RabbitMQ, Kafka, Redis, and Elasticsearch examples require compatible test endpoints and are documented as transport-dependent.