DOWNLOAD MODX 1.0.2

The SendRefererHeader was already on 2. A possible CSRF attempt was detected. May 28th, at 2: January 16th, at 7: I thought about it for a while and it hit me: I have been having this same problem when using Firefox April 13th, at 1:

Uploader:	Shakatilar
Date Added:	3 April 2004
File Size:	25.89 Mb
Operating Systems:	Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads:	22032
Price:	Free* [*Free Regsitration Required]

How to Avoid MODx CSRF Error when Using Firefox - Belafonte Code

It took me over a year to notice that blocking referrer information was actually breaking some functionality on a few sites that 1.02. visit. The Solution Once I realized that mine was set to block, I made the necessary change, and now the problem is fixed. I upgraded from 0.

Home Who Is This… Belafonte? Find out more about me in my obligatory about section. No referer was provided by the server. January 16th, at 7: Some 1.0.2 postings suggest that Norton Anti-Virus may also cause this error. December 28th, at 9: April 13th, at 9: February 3rd, at However, none of these is an actual solution.

ManagerManager

This will block most cross-site cookie tracking, but still allow WordPress and most other sites that depend on referers to function. As I recently mentioned on the forums and on Twitterthe update to version 1.

The good news was that the problem did not seem to appear in Safari, so I was able to get into the manager from there. One of these supposedly helpful suggestions was to instruct Firefox to NOT send referrer information. A possible CSRF attempt was detected.

I actually had my referrers disables from the web developer tool bar, this post saved me a lot of searching and unnecessary trouble! Nice write up either way.

I do have a strict M0n0wall protection for my ISP, but this is runs locally! If you are having this problem and Firefox is not the culprit, you might have some other software on your computer that is blocking the sending of referrer information in an effort to protect your privacy.

For awhile I thought you were having a Firefox on Mac issue. April 13th, at 1: Hey, I just installed 1. I thought about it for a while and it hit me: Setting sendRefererHeader to 2 the default sends it when following links and when loading images on the page.

This could mean this CSRF attack came from within? I 1.00.2 all of these and they do work. The lack of a referrer made me think of the Firefox about: The error shows up like this: I have been having this same problem when using Firefox Modifying the setting in about: Thanks for the tip!

Is it too hard to do it right with unique random tokens?

I think that article on Optimizing Firefox came from LifeHacker. The SendRefererHeader was already on 2. Once I realized that mine was set to block, I made the necessary change, and now the problem is fixed.