Closed
Bug 1234948
Opened 9 years ago
Closed 9 years ago
there is no option to override port
Categories
(Firefox :: Security, defect)
Tracking
()
People
(Reporter: illumilor.e, Unassigned)
References
()
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 2015103000
Steps to reproduce:
When using firefox to navigate to port 79, there is no override option given to the user
Comment 1•9 years ago
|
||
Hi reporter,
unfortunately this report is not very useful because it does not describe the problem well. If you have time and can still reproduce the problem, please read https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines and add a more useful description to this report.
Flags: needinfo?(illumilor.e)
Comment 3•9 years ago
|
||
See https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines as pointed out many many times to you already.
Unfortunately you seem to continue ignoring those bug writing guidelines hence your reports often become a time sink for anybody else looking at them, which is rather disrespectful towards other members of the Mozilla community.
Flags: needinfo?(illumilor.e)
Reporter | ||
Comment 4•9 years ago
|
||
I have followed all the guidelines.What info do you need?
Flags: needinfo?(illumilor.e)
Comment 5•9 years ago
|
||
Please provide precise steps to reproduce the problem (testcase) that allow anybody else to run into the very same problem. Also provide expected results and actual results. These are three different sections.
Flags: needinfo?(illumilor.e)
Reporter | ||
Comment 6•9 years ago
|
||
1. Go to some url that has a blocked port such as 79.
Expected results: an option to override the "you can't access this port" error be given
actual results: no option is give.
I gave all this information in the bug description.
Flags: needinfo?(illumilor.e)
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Component: Untriaged → Security
Resolution: --- → DUPLICATE
Comment 8•9 years ago
|
||
(In reply to illumilor.e from comment #6)
> 1. Go to some url that has a blocked port such as 79.
> Expected results: an option to override the "you can't access this port"
> error be given
> actual results: no option is give.
>
> I gave all this information in the bug description.
No you did not. You only dropped some short sentence without any steps to reproduce, and even your last comment here is still not sufficient because you do not provide a clear testcase and only write "some url". Without being specific, noone will try to guess what your steps to reproduce are.
Reporter | ||
Comment 9•9 years ago
|
||
"and even your last comment here is still not sufficient because you do not provide a clear testcase and only write "some url"."
The exact url is http://192.168.0.1:79/
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Comment 10•9 years ago
|
||
(In reply to illumilor.e from comment #9)
> "and even your last comment here is still not sufficient because you do not
> provide a clear testcase and only write "some url"."
>
> The exact url is http://192.168.0.1:79/
Why you think this is not a dupe?
Flags: needinfo?(illumilor.e)
Comment 11•9 years ago
|
||
illuminor.e: Do not change the status or resolution of a bug report. You can *propose* a status or resolution change *in a comment*.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 12•9 years ago
|
||
I was providing the information that was asked.
Flags: needinfo?(illumilor.e)
You need to log in
before you can comment on or make changes to this bug.
Description
•