DevHeads.net

Bug #64929 [NEW]: Bugtracker rejects legitimate and useful comments as spam

Operating system:
PHP version: Irrelevant
Package: Website problem
Bug Type: Bug
Bug description:Bugtracker rejects legitimate and useful comments as spam

Description:
I am desperately trying to post a snippet of code that triggers a PHP
crash,
hence contributing valuable information to help fix a tremendous bug, but
the
broken paranoid antispam system rejects it saying "please don't spam our
bug
tracker".

(and all it accomplishes is to generate in me a strong desire to flood the

bugtracker with lots of _real_ spam for pure vengeance.)

And I can't even post the example text that triggers the bogus antispam
rejection, because THIS very form is rejecting it as spam as well.
So the bug is preventing from fixing itself.

Drop me an email at mat teo sis ti sett e [at] gma il [dot] com and I'll
reply
with the text that triggers the bogus antismap.
(if you are interested in fixing this issue at all)

Expected result:
Actual result:

Comments

Bug #64929 [Com]: Bugtracker rejects legitimate

By tim dot slot at... at 05/28/2013 - 14:22

Edit report at <a href="https://bugs.php.net/bug.php?id=64929&amp;edit=1" title="https://bugs.php.net/bug.php?id=64929&amp;edit=1">https://bugs.php.net/bug.php?id=64929&amp;edit=1</a>

ID: 64929
Comment by: matteosistisette at gmail dot com
Reported by: matteosistisette at gmail dot com
Summary: Bugtracker rejects legitimate and useful comments as
spam
Status: Open
Type: Bug
Package: Website problem
PHP Version: Irrelevant
Block user comment: N
Private report: N

New Comment:

Can anybody tell me what it has that looks like spam?

Previous Comments:
OK I FOUND IT: it's this code: I'll insert random spaces in it:

if ( $ e xc ep tio n in sta nce of S Exc e pti on ) {

[OMITTING LINE THAT SEEMS TO BE PROBLEMATIC]
http_response_code($exception->getCode());
}else http_response_code(500);
header("Content-Type: text/plain");
S::error($output=$exception->getMessage()." \n @ ".$exception-
set_exception_handler(function($exception) {

Good catch.

Here is my error handler (and also my exception handler though I don't think
it's involved)

set_error_handler(function($errno, $errstr, $errfile, $errline){
http_response_code(500);
header("Content-Type: text/plain");
$backtrace=debug_backtrace();
$output="$errstr \n @ $errfile($errline)\n";
foreach ($backtrace as $i=>$item) {
//if (isset($item['args'])) print_r($item['args']);
if ($i>0) $output.= "#$i. @ ".$item['file']."
(".$item['line']."): ".(isset($item['class'])?
$item['class']:'')."::".$item['function']."(".(is_array($item['args'])?
@implode(",",$item['args']):'').")\n";
}
S::error($output);
die($output);
});

No, Not even a single url.

Now it seems like it's not the @'s.
I tried to post a code that included a error handler and an exception handler.
When I posted only the error handler it was accepted. I'll try to post the whole
message in pieces.

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

<a href="https://bugs.php.net/bug.php?id=64929" title="https://bugs.php.net/bug.php?id=64929">https://bugs.php.net/bug.php?id=64929</a>

Bug #64929 [Com]: Bugtracker rejects legitimate

By tim dot slot at... at 05/28/2013 - 14:21

Edit report at <a href="https://bugs.php.net/bug.php?id=64929&amp;edit=1" title="https://bugs.php.net/bug.php?id=64929&amp;edit=1">https://bugs.php.net/bug.php?id=64929&amp;edit=1</a>

ID: 64929
Comment by: matteosistisette at gmail dot com
Reported by: matteosistisette at gmail dot com
Summary: Bugtracker rejects legitimate and useful comments as
spam
Status: Open
Type: Bug
Package: Website problem
PHP Version: Irrelevant
Block user comment: N
Private report: N

New Comment:

OK I FOUND IT: it's this code: I'll insert random spaces in it:

if ( $ e xc ep tio n in sta nce of S Exc e pti on ) {

Previous Comments:
[OMITTING LINE THAT SEEMS TO BE PROBLEMATIC]
http_response_code($exception->getCode());
}else http_response_code(500);
header("Content-Type: text/plain");
S::error($output=$exception->getMessage()." \n @ ".$exception-
set_exception_handler(function($exception) {

Good catch.

Here is my error handler (and also my exception handler though I don't think
it's involved)

set_error_handler(function($errno, $errstr, $errfile, $errline){
http_response_code(500);
header("Content-Type: text/plain");
$backtrace=debug_backtrace();
$output="$errstr \n @ $errfile($errline)\n";
foreach ($backtrace as $i=>$item) {
//if (isset($item['args'])) print_r($item['args']);
if ($i>0) $output.= "#$i. @ ".$item['file']."
(".$item['line']."): ".(isset($item['class'])?
$item['class']:'')."::".$item['function']."(".(is_array($item['args'])?
@implode(",",$item['args']):'').")\n";
}
S::error($output);
die($output);
});

No, Not even a single url.

Now it seems like it's not the @'s.
I tried to post a code that included a error handler and an exception handler.
When I posted only the error handler it was accepted. I'll try to post the whole
message in pieces.

I'm guessing you are attempting to post text with a bunch of URLs. Is that true?

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

<a href="https://bugs.php.net/bug.php?id=64929" title="https://bugs.php.net/bug.php?id=64929">https://bugs.php.net/bug.php?id=64929</a>

Bug #64929 [Com]: Bugtracker rejects legitimate

By tim dot slot at... at 05/28/2013 - 14:20

Edit report at <a href="https://bugs.php.net/bug.php?id=64929&amp;edit=1" title="https://bugs.php.net/bug.php?id=64929&amp;edit=1">https://bugs.php.net/bug.php?id=64929&amp;edit=1</a>

ID: 64929
Comment by: matteosistisette at gmail dot com
Reported by: matteosistisette at gmail dot com
Summary: Bugtracker rejects legitimate and useful comments as
spam
Status: Open
Type: Bug
Package: Website problem
PHP Version: Irrelevant
Block user comment: N
Private report: N

New Comment:

[OMITTING LINE THAT SEEMS TO BE PROBLEMATIC]
http_response_code($exception->getCode());
}else http_response_code(500);
header("Content-Type: text/plain");
S::error($output=$exception->getMessage()." \n @ ".$exception-

Previous Comments:
set_exception_handler(function($exception) {

Good catch.

Here is my error handler (and also my exception handler though I don't think
it's involved)

set_error_handler(function($errno, $errstr, $errfile, $errline){
http_response_code(500);
header("Content-Type: text/plain");
$backtrace=debug_backtrace();
$output="$errstr \n @ $errfile($errline)\n";
foreach ($backtrace as $i=>$item) {
//if (isset($item['args'])) print_r($item['args']);
if ($i>0) $output.= "#$i. @ ".$item['file']."
(".$item['line']."): ".(isset($item['class'])?
$item['class']:'')."::".$item['function']."(".(is_array($item['args'])?
@implode(",",$item['args']):'').")\n";
}
S::error($output);
die($output);
});

No, Not even a single url.

Now it seems like it's not the @'s.
I tried to post a code that included a error handler and an exception handler.
When I posted only the error handler it was accepted. I'll try to post the whole
message in pieces.

I'm guessing you are attempting to post text with a bunch of URLs. Is that true?

Ok, no, it's the combination of @ more something else.
However, removing the @'s from the snipped of code allowed me to post it.

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

<a href="https://bugs.php.net/bug.php?id=64929" title="https://bugs.php.net/bug.php?id=64929">https://bugs.php.net/bug.php?id=64929</a>

Bug #64929 [Com]: Bugtracker rejects legitimate

By tim dot slot at... at 05/28/2013 - 14:19

Edit report at <a href="https://bugs.php.net/bug.php?id=64929&amp;edit=1" title="https://bugs.php.net/bug.php?id=64929&amp;edit=1">https://bugs.php.net/bug.php?id=64929&amp;edit=1</a>

ID: 64929
Comment by: matteosistisette at gmail dot com
Reported by: matteosistisette at gmail dot com
Summary: Bugtracker rejects legitimate and useful comments as
spam
Status: Open
Type: Bug
Package: Website problem
PHP Version: Irrelevant
Block user comment: N
Private report: N

New Comment:

set_exception_handler(function($exception) {

Previous Comments:
Good catch.

Here is my error handler (and also my exception handler though I don't think
it's involved)

set_error_handler(function($errno, $errstr, $errfile, $errline){
http_response_code(500);
header("Content-Type: text/plain");
$backtrace=debug_backtrace();
$output="$errstr \n @ $errfile($errline)\n";
foreach ($backtrace as $i=>$item) {
//if (isset($item['args'])) print_r($item['args']);
if ($i>0) $output.= "#$i. @ ".$item['file']."
(".$item['line']."): ".(isset($item['class'])?
$item['class']:'')."::".$item['function']."(".(is_array($item['args'])?
@implode(",",$item['args']):'').")\n";
}
S::error($output);
die($output);
});

No, Not even a single url.

Now it seems like it's not the @'s.
I tried to post a code that included a error handler and an exception handler.
When I posted only the error handler it was accepted. I'll try to post the whole
message in pieces.

I'm guessing you are attempting to post text with a bunch of URLs. Is that true?

Ok, no, it's the combination of @ more something else.
However, removing the @'s from the snipped of code allowed me to post it.

test @ test

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

<a href="https://bugs.php.net/bug.php?id=64929" title="https://bugs.php.net/bug.php?id=64929">https://bugs.php.net/bug.php?id=64929</a>

Bug #64929 [Com]: Bugtracker rejects legitimate

By tim dot slot at... at 05/28/2013 - 14:18

Edit report at <a href="https://bugs.php.net/bug.php?id=64929&amp;edit=1" title="https://bugs.php.net/bug.php?id=64929&amp;edit=1">https://bugs.php.net/bug.php?id=64929&amp;edit=1</a>

ID: 64929
Comment by: matteosistisette at gmail dot com
Reported by: matteosistisette at gmail dot com
Summary: Bugtracker rejects legitimate and useful comments as
spam
Status: Open
Type: Bug
Package: Website problem
PHP Version: Irrelevant
Block user comment: N
Private report: N

New Comment:

Good catch.

Here is my error handler (and also my exception handler though I don't think
it's involved)

set_error_handler(function($errno, $errstr, $errfile, $errline){
http_response_code(500);
header("Content-Type: text/plain");
$backtrace=debug_backtrace();
$output="$errstr \n @ $errfile($errline)\n";
foreach ($backtrace as $i=>$item) {
//if (isset($item['args'])) print_r($item['args']);
if ($i>0) $output.= "#$i. @ ".$item['file']."
(".$item['line']."): ".(isset($item['class'])?
$item['class']:'')."::".$item['function']."(".(is_array($item['args'])?
@implode(",",$item['args']):'').")\n";
}
S::error($output);
die($output);
});

Previous Comments:
No, Not even a single url.

Now it seems like it's not the @'s.
I tried to post a code that included a error handler and an exception handler.
When I posted only the error handler it was accepted. I'll try to post the whole
message in pieces.

I'm guessing you are attempting to post text with a bunch of URLs. Is that true?

Ok, no, it's the combination of @ more something else.
However, removing the @'s from the snipped of code allowed me to post it.

test @ test

UNBELIEVABLE.
What causes the bugtracker to reject the message as spam is the mere precence of
the "at" character (you know, the one used in emails).

How can you rely on such a demential method to detect spam?

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

<a href="https://bugs.php.net/bug.php?id=64929" title="https://bugs.php.net/bug.php?id=64929">https://bugs.php.net/bug.php?id=64929</a>

Bug #64929 [Opn]: Bugtracker rejects legitimate

By tim dot slot at... at 05/28/2013 - 14:17

Edit report at <a href="https://bugs.php.net/bug.php?id=64929&amp;edit=1" title="https://bugs.php.net/bug.php?id=64929&amp;edit=1">https://bugs.php.net/bug.php?id=64929&amp;edit=1</a>

ID: 64929
User updated by: matteosistisette at gmail dot com
Reported by: matteosistisette at gmail dot com
Summary: Bugtracker rejects legitimate and useful comments as
spam
Status: Open
Type: Bug
Package: Website problem
PHP Version: Irrelevant
Block user comment: N
Private report: N

New Comment:

No, Not even a single url.

Now it seems like it's not the @'s.
I tried to post a code that included a error handler and an exception handler.
When I posted only the error handler it was accepted. I'll try to post the whole
message in pieces.

Previous Comments:
I'm guessing you are attempting to post text with a bunch of URLs. Is that true?

Ok, no, it's the combination of @ more something else.
However, removing the @'s from the snipped of code allowed me to post it.

test @ test

UNBELIEVABLE.
What causes the bugtracker to reject the message as spam is the mere precence of
the "at" character (you know, the one used in emails).

How can you rely on such a demential method to detect spam?

Description:
I am desperately trying to post a snippet of code that triggers a PHP crash,
hence contributing valuable information to help fix a tremendous bug, but the
broken paranoid antispam system rejects it saying "please don't spam our bug
tracker".

(and all it accomplishes is to generate in me a strong desire to flood the
bugtracker with lots of _real_ spam for pure vengeance.)

And I can't even post the example text that triggers the bogus antispam
rejection, because THIS very form is rejecting it as spam as well.
So the bug is preventing from fixing itself.

Drop me an email at mat teo sis ti sett e [at] gma il [dot] com and I'll reply
with the text that triggers the bogus antismap.
(if you are interested in fixing this issue at all)

Expected result:
Actual result:

Bug #64929 [Opn]: Bugtracker rejects legitimate

By =?utf-8?q?Phili... at 05/28/2013 - 14:03

Edit report at <a href="https://bugs.php.net/bug.php?id=64929&amp;edit=1" title="https://bugs.php.net/bug.php?id=64929&amp;edit=1">https://bugs.php.net/bug.php?id=64929&amp;edit=1</a>

ID: 64929
Updated by: <a href="mailto: ... at php dot net"> ... at php dot net</a>
Reported by: matteosistisette at gmail dot com
Summary: Bugtracker rejects legitimate and useful comments as
spam
Status: Open
Type: Bug
Package: Website problem
PHP Version: Irrelevant
Block user comment: N
Private report: N

New Comment:

I'm guessing you are attempting to post text with a bunch of URLs. Is that true?

Previous Comments:
Ok, no, it's the combination of @ more something else.
However, removing the @'s from the snipped of code allowed me to post it.

test @ test

UNBELIEVABLE.
What causes the bugtracker to reject the message as spam is the mere precence of
the "at" character (you know, the one used in emails).

How can you rely on such a demential method to detect spam?

Description:
I am desperately trying to post a snippet of code that triggers a PHP crash,
hence contributing valuable information to help fix a tremendous bug, but the
broken paranoid antispam system rejects it saying "please don't spam our bug
tracker".

(and all it accomplishes is to generate in me a strong desire to flood the
bugtracker with lots of _real_ spam for pure vengeance.)

And I can't even post the example text that triggers the bogus antispam
rejection, because THIS very form is rejecting it as spam as well.
So the bug is preventing from fixing itself.

Drop me an email at mat teo sis ti sett e [at] gma il [dot] com and I'll reply
with the text that triggers the bogus antismap.
(if you are interested in fixing this issue at all)

Expected result:
Actual result:

Bug #64929 [Com]: Bugtracker rejects legitimate

By tim dot slot at... at 05/27/2013 - 11:16

Edit report at <a href="https://bugs.php.net/bug.php?id=64929&amp;edit=1" title="https://bugs.php.net/bug.php?id=64929&amp;edit=1">https://bugs.php.net/bug.php?id=64929&amp;edit=1</a>

ID: 64929
Comment by: matteosistisette at gmail dot com
Reported by: matteosistisette at gmail dot com
Summary: Bugtracker rejects legitimate and useful comments as
spam
Status: Open
Type: Bug
Package: Website problem
PHP Version: Irrelevant
Block user comment: N
Private report: N

New Comment:

Ok, no, it's the combination of @ more something else.
However, removing the @'s from the snipped of code allowed me to post it.

Previous Comments:
test @ test

UNBELIEVABLE.
What causes the bugtracker to reject the message as spam is the mere precence of
the "at" character (you know, the one used in emails).

How can you rely on such a demential method to detect spam?

Description:
I am desperately trying to post a snippet of code that triggers a PHP crash,
hence contributing valuable information to help fix a tremendous bug, but the
broken paranoid antispam system rejects it saying "please don't spam our bug
tracker".

(and all it accomplishes is to generate in me a strong desire to flood the
bugtracker with lots of _real_ spam for pure vengeance.)

And I can't even post the example text that triggers the bogus antispam
rejection, because THIS very form is rejecting it as spam as well.
So the bug is preventing from fixing itself.

Drop me an email at mat teo sis ti sett e [at] gma il [dot] com and I'll reply
with the text that triggers the bogus antismap.
(if you are interested in fixing this issue at all)

Expected result:
Actual result:

Bug #64929 [Com]: Bugtracker rejects legitimate

By tim dot slot at... at 05/27/2013 - 11:15

Edit report at <a href="https://bugs.php.net/bug.php?id=64929&amp;edit=1" title="https://bugs.php.net/bug.php?id=64929&amp;edit=1">https://bugs.php.net/bug.php?id=64929&amp;edit=1</a>

ID: 64929
Comment by: matteosistisette at gmail dot com
Reported by: matteosistisette at gmail dot com
Summary: Bugtracker rejects legitimate and useful comments as
spam
Status: Open
Type: Bug
Package: Website problem
PHP Version: Irrelevant
Block user comment: N
Private report: N

New Comment:

test @ test

Previous Comments:
UNBELIEVABLE.
What causes the bugtracker to reject the message as spam is the mere precence of
the "at" character (you know, the one used in emails).

How can you rely on such a demential method to detect spam?

Description:
I am desperately trying to post a snippet of code that triggers a PHP crash,
hence contributing valuable information to help fix a tremendous bug, but the
broken paranoid antispam system rejects it saying "please don't spam our bug
tracker".

(and all it accomplishes is to generate in me a strong desire to flood the
bugtracker with lots of _real_ spam for pure vengeance.)

And I can't even post the example text that triggers the bogus antispam
rejection, because THIS very form is rejecting it as spam as well.
So the bug is preventing from fixing itself.

Drop me an email at mat teo sis ti sett e [at] gma il [dot] com and I'll reply
with the text that triggers the bogus antismap.
(if you are interested in fixing this issue at all)

Expected result:
Actual result:

Bug #64929 [Com]: Bugtracker rejects legitimate

By tim dot slot at... at 05/27/2013 - 11:15

Edit report at <a href="https://bugs.php.net/bug.php?id=64929&amp;edit=1" title="https://bugs.php.net/bug.php?id=64929&amp;edit=1">https://bugs.php.net/bug.php?id=64929&amp;edit=1</a>

ID: 64929
Comment by: matteosistisette at gmail dot com
Reported by: matteosistisette at gmail dot com
Summary: Bugtracker rejects legitimate and useful comments as
spam
Status: Open
Type: Bug
Package: Website problem
PHP Version: Irrelevant
Block user comment: N
Private report: N

New Comment:

UNBELIEVABLE.
What causes the bugtracker to reject the message as spam is the mere precence of
the "at" character (you know, the one used in emails).

How can you rely on such a demential method to detect spam?

Previous Comments:
Description:
I am desperately trying to post a snippet of code that triggers a PHP crash,
hence contributing valuable information to help fix a tremendous bug, but the
broken paranoid antispam system rejects it saying "please don't spam our bug
tracker".

(and all it accomplishes is to generate in me a strong desire to flood the
bugtracker with lots of _real_ spam for pure vengeance.)

And I can't even post the example text that triggers the bogus antispam
rejection, because THIS very form is rejecting it as spam as well.
So the bug is preventing from fixing itself.

Drop me an email at mat teo sis ti sett e [at] gma il [dot] com and I'll reply
with the text that triggers the bogus antismap.
(if you are interested in fixing this issue at all)

Expected result:
Actual result: