Failing to signon to Macy's web site & receive 'A technical error has occurred. For assistance, please call' missive. 的最新解答https://support.mozilla.org/zh-TW/questions/12635622019-06-30T03:16:23-07:00Thank you for your quick response. I followed all instructions for Cookies, Content and Cache. still2019-06-30T03:16:23-07:00cornysthttps://support.mozilla.org/zh-TW/questions/1263562#answer-1234013<p>Thank you for your quick response. I followed all instructions for Cookies, Content and Cache. still no joy! I don't believe that it is a Firefox issue at all.
</p><p>FYI, I was able to sign in, successfully, via Windows 10 Mobile Microsoft Edge.
</p><p>Again thank you for quick respose and suggestions.
Cornyst
</p>What Firefox version do you use?
Are you possibly using "Resist Fingerprinting"?
https://support.mo2019-06-30T03:08:28-07:00cor-elhttps://support.mozilla.org/zh-TW/questions/1263562#answer-1234011<p>What Firefox version do you use?
</p><p>Are you possibly using "Resist Fingerprinting"?
</p>
<ul><li><a href="https://support.mozilla.org/en-US/kb/firefox-protection-against-fingerprinting" rel="nofollow">https://support.mozilla.org/en-US/kb/firefox-protection-against-fingerprinting</a>
</li></ul>
<p>You can check this pref on the <b>about:config</b> page to see if resist fingerprinting (RFP) is enabled and if this pref is user set (bold) reset to false via the right-click context menu.
</p>
<ul><li>privacy.resistFingerprinting = false
</li></ul>
<p>You can open the <b>about:config</b> page via the location/address bar.
You can accept the warning and click "I accept the risk!" to continue.
</p>
<ul><li><a href="https://support.mozilla.org/en-US/kb/about-config-editor-firefox" rel="nofollow">https://support.mozilla.org/en-US/kb/about-config-editor-firefox</a>
</li></ul>They didn't give you much to go on, did they?
Websites use a series of test to try to prevent automa2019-06-30T00:46:38-07:00jscher2000https://support.mozilla.org/zh-TW/questions/1263562#answer-1233958<p>They didn't give you much to go on, did they?
</p><p>Websites use a series of test to try to prevent automated access, so possibly something about the way your Firefox responded was considered suspicious. Possibly some blocked content, blocked cookies, blocked storage, or modified headers is a factor. If you've done any customization to make Firefox load less crap or share less data, it's possible that is the problem, but unless someone wants to test the site with lots of different settings, I don't know that we'd come up with a definitive diagnosis.
</p><p>For future reference, you might look at cookie settings and Content Blocking as the most obvious potential culprits. If it's a site you have visited in Firefox in the past, clearing the cache can also help to avoid a mismatch of old and new files. Some articles:
</p>
<ul><li> <a href="/en-US/kb/websites-say-cookies-are-blocked-unblock-them" rel="nofollow">Websites say cookies are blocked - Unblock them</a>
</li><li> <a href="/en-US/kb/content-blocking" rel="nofollow">Content blocking</a>
</li><li> <a href="/en-US/kb/how-clear-firefox-cache" rel="nofollow">How to clear the Firefox cache</a>
</li></ul>