<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Charles on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/charles/</link>
    <description>Recent content in Charles on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Dec 2022 22:25:45 -0500</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/charles/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Modifying incoming requests via Charles Proxy</title>
      <link>https://www.bradcypert.com/modifying-incoming-requests-via-charles-proxy/</link>
      <pubDate>Thu, 08 Mar 2018 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/modifying-incoming-requests-via-charles-proxy/</guid>
      <description>&lt;p&gt;Charles Proxy is an outstanding development tool that I’ve recently started to fall in love with. I think the most practical use of this tool is probably using the rewrite tool to rewrite outgoing or incoming requests, however, I’m going to talk to you about setting up request breakpoints. Breakpoints allow you to halt an incoming or outgoing requests, possibly modify it, and send it whenever you’re content with it. It’s a fantastic tool for simulating edge-cases like making an http request to a server that wraps and returns the response of a request that it makes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
