In addition to just the part that matches regex.
(In reply to comment #2)
I'm still not completely comfortable with the idea of logging full
(blacklisted) URLs like this. I think this may have been an intentional
Anyway in contrast, abuse log (Extension:AbuseFilter) contains every detail of an editing action, even when it's rejected.
I think this REALLY should be added ASAP - spammers use redirects to spam their sites anyway, and hits like 'goo.gl', 'ow.ly', and 'tinyurl.com' do not help at all. Having the full link enables us to find what is being linked to, and whether or not the spam problem still exists (please, do 'disable' the links by removing the 'http://'-part, no need to accidentally click a bad link). Thanks! --~~~~
(In reply to Kunal Mehta (Legoktm) from comment #1)
I'm not sure if there will be a simple way to do this without breaking b/c...
What's your concern re: breakage? Is the content of Special:Log being parsed by things that expect just the matching domain? Or is the worry that regexes shared between wikis running different versions of this extension would be inconsistent? The patch I submitted shouldn't have the latter problem, as it constructs a full-line-matching regex for logs only when the initial regex detects a match.
Imo, this would be the best approach : a link to a page with details on the attempted edit similar to the abuse filter one, i.e. with the diff, new wikitext, old wikitext, etc (example). No risk to click the link that way and it can be restricted. Having the link(s) in context would provide much more information on the user intention. Dunno about feasibility or if the AF code can be adapted, though.