Summary | Error loging out. Required secret is invalid - potentially malicious request. |
Queue | Horde Groupware Webmail Edition |
Queue Version | 1.1 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | |
Requester | k11h12anh (at) gmail (dot) com |
Created | 06/06/2008 (6276 days ago) |
Due | |
Updated | 07/13/2008 (6239 days ago) |
Assigned | 06/06/2008 (6276 days ago) |
Resolved | 07/13/2008 (6239 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Not A Bug
down yourself we can't do anything about that issue.
bug #6673and fixed with thepatch linked from that ticket?
operations work fine but when you are in the Turba pages and try to
logout, you get the error.
imap) and logout and do nothing between this two actions to provoke
this token-error. I'm using MySQL for storage, sessions and tokens,
too. I think the problem is, that only sessionhandler-table is set to
InnoDB engine, and so there are row-lock problems. The token-table
uses MyIsam, so I changed it to InnoDB (ALTER TABLE horde_tokens
ENGINE=InnoDB;) and it seems to works. By the way I've applied this
engine to all tables.
bug #6673and fixed with thepatch linked from that ticket?
imap) and logout and do nothing between this two actions to provoke
this token-error. I'm using MySQL for storage, sessions and tokens,
too. I think the problem is, that only sessionhandler-table is set to
InnoDB engine, and so there are row-lock problems. The token-table
uses MyIsam, so I changed it to InnoDB (ALTER TABLE horde_tokens
ENGINE=InnoDB;) and it seems to works. By the way I've applied this
engine to all tables.
it. Here is how you get to the error:
On Horde's Custom Session Handler setup tab, choose the MySQL session
handlers then save the config. This setting causes the error. I also
noticed the check for enabling row-level locking. Disabling this gets
rid of the error but then you get a different error and your Address
Book disappears and you cannot create a new one.
doesn't work either. For example, adding a contact gives the same
error message. I also found these errors in httpd log:
[Wed Jun 11 14:17:44 2008] [error] [client 192.168.110.33] PHP
Warning: mysql_error(): 18 is not a valid MySQL-Link resource in
/var/www/html/horde/lib/Horde/SessionHandler/mysql.php on line 173,
referer:
https://pop.domainname.com/horde/index.php?url=https%3A%2F%2Fpop.domainname.com%2Fhorde%2Fimp%2Fmailbox.php%3Fmailbox%3DINBOX%26mailbox_token%3D851e7112c2ee85c092533ebed502b569
[Wed Jun 11 14:17:46 2008] [error] [client 192.168.110.33] PHP
Warning: mysql_error(): 18 is not a valid MySQL-Link resource in
/var/www/html/horde/lib/Horde/SessionHandler/mysql.php on line 173,
referer:
https://pop.domainname.com/horde/imp/mailbox.php?mailbox=INBOX&mailbox_token=851e7112c2ee85c092533ebed502b569&frameset_loaded=1
[Wed Jun 11 14:18:06 2008] [error] [client 192.168.110.13] PHP
Warning: mysql_error(): 18 is not a valid MySQL-Link resource in
/var/www/html/horde/lib/Horde/SessionHandler/mysql.php on line 173,
referer: https://pop.domainname.com/horde/services/portal/sidebar.php
disabling it but logout still didn't work. Log file didn't show
anything because I think this isn't really an error, it's something
that just doesn't work. Are you using the stable Horde Groupware
Webmail Edition 1.1 with MySQL?
Try looking for errors in the log files and try to configure a
different Token driver.
State ⇒ Feedback
Try looking for errors in the log files and try to configure a
different Token driver.
Milestone ⇒
State ⇒ Unconfirmed
Patch ⇒ No
Queue ⇒ Horde Groupware Webmail Edition
Summary ⇒ Error loging out. Required secret is invalid - potentially malicious request.
Type ⇒ Bug
Priority ⇒ 1. Low
gives an error "Required secret is invalid - potentially malicious
request."
Steps to error:
1. Click Address Book
2. Click Options
3. choose and click one of the Options for Address Book
4. click the Log Out button