-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inifinite loop in rcube_washtml->dumpHtml() #4202
Comments
Comment by @alecpl on 17 May 2013 16:21 UTC Please, send the message source to alec at alec dot pl. |
Milestone changed by @alecpl on 17 May 2013 16:21 UTC later => 0.9.1 |
Comment by @alecpl on 17 May 2013 17:05 UTC Got it. The HTML code in the message is very bad. It contains ca. 150 nested tags. I suppose we could detect the limit and just skip the nested content making sure fatal error is not thrown, printing warning to the log instead. |
Comment by @alecpl on 17 May 2013 17:26 UTC The option is xdebug.max_nesting_level or suhosin.executor.max_depth. |
Comment by flack on 22 May 2013 13:08 UTC Ok, I added
to main.inc.php now, and for the moment, this is ok as a workaround. But it would be really good if this situation could be handled more gracefully by RC itself. I mean, the email's HTML was very bad, true, but it was not forged or tampered or anything, so in principle, this problem might occur in every installation, since you never know who sends you what. Maybe there could be some logic that throws an exception right before the max nesting level is reached, and then the message gets displayed as plain text instead of HTML? But that's only off the top of my head, I haven't looked at the actual RC code involved to see if such a thing is possible or desirable. |
Status changed by @alecpl on 24 May 2013 07:21 UTC new => closed |
Milestone changed by @alecpl on 24 May 2013 07:21 UTC 1.0-beta => 0.9.2 |
Comment by jansegre on 4 Apr 2014 21:56 UTC I've recently had this issue with roundcube 0.9.3 and tried upgrading to 0.9.5 and 1.0.0-rc, none of them solve this issue. I took a look at patch that should fix the issue and I encountered this problem: To temporarily fix this problem I changed the signature of the function to: And the problem was gone. (A brief binary search revealed that 17 was the smallest $level that fixed it, though it might not always be the case if my theory is correct) I either overlooked something else or the patch doesn't exactly fix the issue. I can forward the email that started this trouble, I just don't know where to send it to. |
Reported by flack on 17 May 2013 14:06 UTC as Trac ticket #1489110
On some messages in a user mailbox, the following error appears when opening them:
I have a sample message here, but since it contains private information, I don't want to put it on a public bug tracker. I can provide it on request, though
Migrated-From: http://trac.roundcube.net/ticket/1489110
The text was updated successfully, but these errors were encountered: