Closed Bug 214979 Opened 21 years ago Closed 21 years ago

htaccess is a Bugzilla Dirty Word

Categories

(Bugzilla :: Bugzilla-General, defect)

x86
All
defect
Not set
normal

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: SkewerMZ, Assigned: justdave)

Details

See also bug 164572: For security reasons Bugzilla blocks the string "." + "htaccess" to prevent abuse. However this also interferes with normal operation of Bugzilla (particularly evangelism issues). If you write a comment containing that string you get a confusing "no data" error. I suggest we either change the behavior to at least return a better error message or fix it so it is possible to use htaccess in the comments without a problem. It is confusing to tell people to create a new file "dot, and then htaccess"!
Uhh... say what? .htaccess there. is that blocked? Please explain what you mean. I'm lost.
Odd... I will try to reproduce the problem on a different configuration.
My comment worked, and I got what I typed in the email, too. WORKSFORME.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
what version of Bugzilla are you running? I bet it's old... we used to have a bug with sending mail via sendmail where it would cut off the email if a line had a leading dot. I forget what version it was fixed in but it was a long time ago.
I had the problem right here. .htaccess ?
Worked in IE, so apparently this isn't Bugzilla's fault......
Status: RESOLVED → VERIFIED
what problem? I'm still lost. Is it disappearing from your comment? does it not show up in the email?
.htaccess
This may be a conflict with Norton Personal Firewall 2003... .htaccess
.htaccess (filter spam: block, um, .htaccess)
Intrusion detection in NPF2003 is the source of the problem. If turned on, when submitting a Bugzilla post (or ANY post) containing .htaccess Norton will for some stupid reason block it causing the "no data" error. Completely independent of anything Bugzilla related, so forget this bug. :)
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.