281956 - You don't have permission to access /core/postfeedback.php on this server.

Status: RESOLVED FIXED

(addons.mozilla.org Graveyard :: Public Pages, defect)

Description

[Portolanus]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I tried to rate cuneAform (and would have been the first). I filled in the form
and clicked [commit]. I was send this page
url=https://update.mozilla.org/core/postfeedback.php?application=firefox&version=1.0&os=Windows
contents:
Forbidden
You don't have permission to access /core/postfeedback.php on this server.
Apache/2.0.46 (Red Hat) Server at update.mozilla.org Port 8080


Reproducible: Always

Steps to Reproduce:
1. menu:Tools,Extensions,get more extensions,Developer tools
2. in table cuneAform, select Robin Monks, cuneAform, Rate It!
3. fileld in all field and pressed commit.

Actual Results:  
A was presented with a webpage saying I have no permission to access
/core/posfeedback.php

Expected Results:  
Accept the rating of course!


After the first time, I looked up the possibility of reporting a bug. As you can
see by my comment here, I have an account by now.
Even with that account and logged in in another window of Firefox, I caanot rate
the extension.

Comment 1

[alanjstr]

Now you shouldn't be able to even get to the Rate It form.

Comment 2

[Portolanus]

Well that makes me really happy. This answers everything.
Is this your way of telling me that Bugzilla no longer allows people to rate
extensions? Or is it something personal?

Comment 3

[Portolanus]

This reminds me of an issue several thousand people had with an internet
company. This company had a great idea to resolve all of their problems in one
strike.
"To reduce complaints about our service, we no longer offer any service."

Comment 4

[alanjstr]

1) Bugzilla has nothing to do with rating extensions
2) You shouldn't have been able to get to that page in the first place.  We
missed it when we disabled the page.  The bug in our code which is the link
which leads to the 403, has been fixed.
3) We already have at least one other bug about things being disabled on purpose.