Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a url that I'm hitting that works in incognito mode, Firefox, Safari, and pretty much any other browser other than vanilla Chrome. If I curl the url, it returns 200.

For whatever reason, Chrome is caching an old redirect for the url. I've tried completely wiping all cache and history to no avail.

How do I fix this and is there anything else I can do to test why this is happening?

share|improve this question

migrated from Jun 20 '13 at 5:30

This question came from our site for professional and enthusiast programmers.


1.Add a unique suffix to the URL, this will avoid the cache. Example: Original URL, change it to or

2.Use Chrome built in Developer tools and watch the newtwork tab

share|improve this answer

As it turns out, I use a chrome extension called HTTPS Everywhere which comes with rules about how to redirect certain sites to the secured version. In my case, HTTPS Everywhere was matching a Formstack url I was trying to access and incorrectly redirecting it to the wrong url.

There is a bug in the rules for Formstack which incorrectly redirects:


To this:

Here's the incorrect rule:

Ruleset Path: /Users/MYUSER/Library/Application Support/Google/Chrome/Default/Extensions/gcbommkclmclpchllfjekcdonpmejbdp/2013.6.4_0/rules/default.rulesets

<ruleset f="Formstack.xml" name="Formstack (partial)">
    <target host=""/>
    <target host="*"/>
    <exclusion pattern="^http://www\.formstack\.com/forms/$"/>
    <rule from="^http://(www\.)?formstack\.com/" to="https://$"/>
    <rule from="^http://blog\.formstack\.com/favicon\.ico$" to=""/>
    <rule from="^http://(?:blog\.formstack\.com/wp-content/themes/fontstack-theme|\.jpg$" to=""/>

To fix, change this line:

<rule from="^http://(www\.)?formstack\.com/" to="https://$"/>


<rule from="^http://(www\.)?formstack\.com/" to="https://$"/>

After updating the rule, simply disable and then disable the extension and it should take effect right away.

I'm not sure why the exclusion pattern didn't match for my url, but nevertheless, the fix above works for me. If I get some time, I might submit it back to the project.

Hope this helps!

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .