HTTP Inspector

Published at August 18, 2020 ·  8 min read

Using the HTTP Inspector built into the Packertriot client will make writing and debugging applications that integrate with webhooks much easier. You’re not limited to webhooks either, you can debug any HTTP-based application. There’s lot of examples we could provide to illustrate how useful an HTTP inspector is during web development. In this post we’ll walk through creating a webhook for a GitHub repository so that we can receive notifications when changes are made to the repo....


Client Update v0.9.19

Published at August 18, 2020 ·  3 min read

This release includes a big update! For a while I’ve gone back and forth about adding an HTTP inspector. I wasn’t sure how difficult it would be to write a decent simple inspector and how muc time and effort would be required. So I delayed this feature and thought it might not be necessary. However, I’ve found it difficult to lure developers to Packetriot and I’ve had several customers and users ask for it since our launch....


Client Update v0.9.17

Published at July 21, 2020 ·  2 min read

This update includes a bug fix for secure redirection, HTTP->HTTPS, that affected traffic on wildcard domains when subsequent HTTP requests utilized POST/PUT/DELETE requests. Technical Details For some more background on this defect, the HTTP requests that pass through Hubs, our edge server software, is updated to included X-Forward-X headers. These header fields are processed by a “forwarder” and “secure-redirect” HTTP handler in the Packetriot client. The forwarder will attempt to set the X-Forwarded-For flag when possible if they were not present (e....


Client Update v0.9.16

Published at June 16, 2020 ·  2 min read

This update includes some bug fixes and some new features. We fixed a dead-lock in our client that preventing tunnels from re-connecting when disconnected so this update is highly recommended. Fixed Dead-Lock We discovered a dead-lock issue that was introduced in an earlier release that impacted clients that used Let’s Encrypt for custom domains. The client periodically checks for opportunities to renew certificates with Let’s Encrypt and then does. This dead-lock would basically lock up any requests to custom domain using Let’s Encrypt after 12 hours....


Client Update v0.9.10

Published at March 23, 2020 ·  3 min read

We added DNS-over-HTTPS support in the last release (v0.9.9). It looks like some users may have had some issues. I think it may be due to some network blocking DNS requests to non-managed servers. E.g (blocking 8.8.8.8, 1.1.1.1, …). Some corporate network admins do this. We’ve added a new flag --doh in the configure command and also a field in the configuration file that can be set so that the client will use DNS-over-HTTPS or not (the local DNS system resolver)....