Hi all,
I'm not sure where I have to put this, but I recently ran across a number of issues regarding my existing installation.
All of a sudden, when I tried editing fields in a view (when an Ajax call is triggered) I get messages like this:
"An error occurred at /nl/admin/build/views/ajax/display/previousblog/default/title."
Actually this is the case for any field.
Further examination via Firebug states the following:
404 Not Found
998ms jquery.js?V (regel 13)
POST http://xxxxxx.org/nl/admin/build/views/ajax/display/previousblog/default...
http://xxxxxx.org/nl/admin/build/views/ajax/display/previousblog/default...404 Not Found
1.02s
I experience the same behaviour in Panels.
Here again, same issue.
My first thought was that this had something to do with Ajax itself, but I had no clue why. So I decided to look at Apache's error logs. I got a bit smarter, with the following message:
[Sun Mar 15 21:32:20 2009] [error] [client 146.175.220.133] ModSecurity: Access denied with code 501 (phase 2). Match of "rx (?:^(?:application\\\\/x-www-form-urlencoded(?:;(?:\\\\s?charset\\\\s?=\\\\s?[\\\\w\\\\d\\\\-]{1,18})?)??$|multipart/form-data;)|text/xml)" against "REQUEST_HEADERS:Content-Type" required. [file "/etc/httpd/conf.d/modsecurity2/modsecurity_crs_30_http_policy.conf"] [line "69"] [id "960010"] [msg "Request content type is not allowed by policy"] [severity "WARNING"] [tag "POLICY/ENCODING_NOT_ALLOWED"] [hostname "xxxxxx.org"] [uri "/nl/admin/build/views/ajax/display/latestnews/default/display_title"] [unique_id "Sb1l1FURxxMAAFXM4VQAAAAA"]
Policy issues, right. But what does that mean?
Then I decided to upgrade Drupal, going from 6.5 to 6.10. Again, this didn't work out for me. More 404 errors started to emerge. For example, I wasn't able to update permissions anymore.
And finally I took a glance at Drupal's db logs:
file_get_contents(sites/all/modules/calendar/js/calendar_colorpicker.js) [function.file-get-contents]: failed to open stream: No such file or directory in /home/imbit/domains/imbit.org/public_html/includes/locale.inc op regel 1685.
and
The specialized Panels menu router rebuild failed. Some paths may not work correctly.
This indicates that it has something to do with a path being wrong. But how do I get that path right again?
I'm sure this is not a theming issue, since the Ajax calls equally don't work in Garland or Blue Marine.
I'm really stuck here.
Your help is much appreciated!
Thanks
- Kris
Comments
Solution
The issue was Apache related. My hosting company has solved the problem and I believe they dissabled mod_security.