Skip to main content

9 posts tagged with "HTTP Debugging"

View All Tags

ModHeader Alternatives: Your Options in 2026

· 9 min read
Daniel Caldas
Co-founder

ModHeader was the default way to change HTTP headers in the browser for years. In July 2026 it was removed from the Chrome Web Store and Edge Add-ons, so many developers who relied on it now need something else for the same job: an Authorization header on a staging API, a feature flag header, a User-Agent override, a CORS header on a local server.

This post covers why people are moving, and the options that cover the job, from a free extension to the browser's own tools. I build tweak, so read with that in mind; each section says what the tool is best for.

How to Redirect a Request to Localhost in Chrome

· 11 min read
Daniel Caldas
Co-founder

The bug only happens on production. The fix is in your editor. Deploying a branch to find out whether it works takes twenty minutes, and you will need three tries. What you want is the production page, with its real data and its real login, talking to the code running on your machine.

That is a redirect: when the page asks for https://api.example.com/... or https://cdn.example.com/app.js, the browser goes to http://localhost instead. This guide shows how to do it in Chrome with a free redirect rule, and the four or five things that will get in your way the first time.

Requestly Alternatives: 7 Tools and What Each Is For

· 9 min read
Daniel Caldas
Co-founder

Requestly does a lot: an HTTP interceptor as a browser extension and a desktop app, a long list of rule types, an API client and team workspaces. That breadth is exactly why some developers look elsewhere. Some only need a mock in one tab and want a smaller tool. Others need more than a browser can see, or want their mocks in code.

This post lists seven alternatives, grouped by the job they do best. I build tweak, so it comes first; every section also says when another tool is the better pick.

Chrome DevTools Network Tab: A Developer's Guide

· 10 min read
Daniel Caldas
Co-founder

The Network tab is where most frontend bugs are actually solved. A blank screen, a spinner that never ends, a form that "does nothing": open the Network tab and the answer is usually one row away. Most developers use about a fifth of it. This guide goes through the rest: the filters, the details panes, the right-click menu, and the features hidden under More tools.

Everything here is Chrome's DevTools, and the same in Edge and other Chromium browsers. Firefox's Network Monitor has most of the same features under slightly different names.

How to Fix CORS Errors in Your Browser

· 8 min read
Daniel Caldas
Co-founder

You call an API from your frontend, the request shows up in the Network tab with a perfectly good response, and your code still gets nothing but this in the console:

Access to fetch at 'https://api.example.com/orders' from origin 'http://localhost:5173'
has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on
the requested resource.

This post explains what the browser is doing, how to read the variations of that message, how to fix it properly, and how to get unblocked right now while you develop, with one click.

Edit HTTP Requests Before Sending (No Proxy Needed)

· 14 min read
Daniel Caldas
Co-founder

You want the next request to go out a little differently. A bigger quantity, an expired token, someone else's id, a field the backend does not support yet. Not forever, just this once, to see what happens.

That is a request breakpoint: stop the request in flight, edit it, let it go. Desktop proxies have done this for twenty years, but they ask you to reroute your traffic and trust a certificate first. This guide shows how to do it from inside the page with tweak's Pause & Edit (previously called Edit before send), which use cases it covers, and how it compares, feature and price, with Charles, Fiddler, Proxyman, Burp Suite and the free tools.

tweak vs Proxyman: Browser Extension or Proxy?

· 6 min read
Daniel Caldas
Co-founder

If you're debugging HTTP requests and network issues, you've likely considered both tweak and Proxyman. Both tools let you intercept, inspect, and modify network traffic, but they approach the problem from different angles. tweak is a lightweight browser extension; Proxyman is a full-featured desktop proxy application. Understanding their differences will help you pick the right one for your workflow.

How to Block a Request URL in Chrome

· 9 min read
Daniel Caldas
Co-founder

You want to know what your app does when one request never arrives. The recommendations API is down: does the product page still render? The analytics script is blocked by a visitor's ad blocker: does checkout still work? The font CDN times out: does the text show at all?

The quickest way to find out is to block that request URL in the browser and look. This guide shows three ways to do it in Chrome, what the page receives when you do, and which one to pick.

How to Mock API Calls in the Browser (2026 Guide)

· 18 min read
Daniel Caldas
Co-founder

To mock an API call is to answer a request your app makes with a response you wrote, instead of the one the server would send. The app cannot tell the difference: it receives the JSON, the status code and the headers you chose, and renders whatever they lead to.

You need it more often than you would think. The endpoint you are building against does not exist yet. A bug only shows up with a payload you cannot reproduce. The staging server is down on demo day. You want to see the screen for a 500, an empty list or a response that takes eight seconds. In all of these, waiting for the backend is the slow option.

This guide covers what mocking is, the three ways to do it and their trade-offs, then shows step by step how to mock a response right in the browser with tweak: no code, no proxy, no change to your app.