Last modified: 2011-11-02 22:15:23 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T18172, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 16172 - # is always taken to begin a comment, even when escaped
# is always taken to begin a comment, even when escaped
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Spam Blacklist (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-29 17:10 UTC by Mike.lifeguard
Modified: 2011-11-02 22:15 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Mike.lifeguard 2008-10-29 17:10:27 UTC
In a regex like
 .*[abc\#].* <newaccountonly>
The hash is taken to be the start of a comment, even when escaped. Hashes should be checked to see if they're escaped - if so it must not be the beginning of a comment (since anything coming before the hash on that line is, by definition, /not/ part of the comment, but instead part of the regex. Any comment beginning with \# is incorrect, but that should be valid within regexes.
Comment 1 Mike.lifeguard 2008-10-29 17:52:49 UTC
(In reply to comment #0)
> In a regex like
>  .*[abc\#].* <newaccountonly>
> The hash is taken to be the start of a comment, even when escaped. Hashes
> should be checked to see if they're escaped - if so it must not be the
> beginning of a comment (since anything coming before the hash on that line is,
> by definition, /not/ part of the comment, but instead part of the regex. Any
> comment beginning with \# is incorrect, but that should be valid within
> regexes.
> 

Doesn't matter for titleblacklist as # is invalid in titles and usernames, but might matter for spam blacklist. If we want to whitelist a specific section or something, it'd be impossible to do so, I think.
Comment 2 Fran Rogers 2008-10-30 22:24:03 UTC
I'm not sure this is necessary. #'s only meaning within URLs is as a [[fragment identifier]] for the client (it's not even sent as part of an HTTP request, so the server never sees it); I can't think of any cases where spam-blacklisting a specific fragment identifier would have any useful purpose.
Comment 3 Mike.lifeguard 2008-10-30 22:26:48 UTC
(In reply to comment #2)
> I'm not sure this is necessary. #'s only meaning within URLs is as a [[fragment
> identifier]] for the client (it's not even sent as part of an HTTP request, so
> the server never sees it); I can't think of any cases where spam-blacklisting a
> specific fragment identifier would have any useful purpose.
> 

No, however the whitelist uses the same syntax. Nonetheless, I can't offhand think of a case where this bug would actually cause problems; it was made on the recommendation of someone else (Splarka, I think).
Comment 4 seth 2011-11-02 22:15:23 UTC
You can use \x23 instead of #. So I guess this ticket is a wontfix candidate?

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links