#259 403 Forbidden after save/drop any SELECT procedure or view

3.4.0
closed-works-for-me
Jakub Vrána
MySQL (65)
5
2012-12-16
2012-07-07
Michele Salvador
No

When I 'Create' / 'Alter' a Procedure or a View that include a SELECT statement
then click 'Save' or 'Drop', a "403 Forbidden" server page always appears.
For example with a simple procedure like:

SELECT * FROM commenti;

This happen only on remote server, not in local machine.
Only if a SELECT is included, not with INSERT.

However everything is okay creating Procedure and View from ' SQL command'

CREATE VIEW foo AS ( SELECT...

I checked all writing / reading / execution authorization for Adminer file and for directory in which Adminer is.

In Privileges -> my Username -> Edit -> 'All privileges' is checked for my database

I'm using Adminer 3.4.0
on remote server Apache 2.2.22
MySQL 5.1.63-community-log
PHP 5.3.10

Please help
Thank you

Discussion

  • Maybe I found the point: the server needs a SQL syntax a little bit more accurate when I create View or Procedure with SELECT to access for example a table 'commenti' :

    SELECT * FROM commenti -- click 'Save' brings to '403 Forbidden'
    SELECT * FROM `commenti` -- ok. procedure/view is saved

    other example of syntax accuracy in procedure / view :

    SELECT id FROM commenti -- brings '403 Forbidden'
    SELECT id AS id FROM commenti -- ok

    Note that also phpMyAdmin has exactly the same behavior.

     
  • Jakub Vrána
    Jakub Vrána
    2012-12-16

    • status: open --> closed-works-for-me
     
  • Jakub Vrána
    Jakub Vrána
    2012-12-16

    It doesn't look like Adminer related, Adminer doesn't emit 403. Maybe there's some layer (Suhosin or such) emitting this code.