404 Forbidden sounds not right

[irinikp]

Preconditions

Magento 2.1

Steps to reproduce

Reopening Issue #5176 as it is still reproducible

[kalpmehta]

Make sure your hosting provider is not blocking it. Are you on nexcess?

[irinikp]

Not on nexcess. I have a dedicated server, there is no blocking

[ekuusela]

The forbidden status is set here:

magento2/app/code/Magento/Backend/Controller/Adminhtml/Noroute/Index.php

Line 37 in b2f688c

$resultPage->setStatusHeader(404, '1.1', 'Forbidden');

[magento-engcom-team]

@irinikp thank you for your report.
Please use the issue reporting guidelines to report an issue. Please, edit issue description and include the preconditions, the steps required to reproduce, the actual result, and the expected result.
Please, add the following information:

• Preconditions: Magento version
• DETAILED Steps to reproduce and enviroument configuration
• Expected result
• Actual result

[korostii]

Hello again @magento-engcom-team
The comment above yours goes as far as pointing out the exact place in source code which ought to be fixed. Putting bureaucracy aside, that's more plenty enough information.

If you insist, it's insanely easy to reproduce: you can even access the page directly.
Here's a CE 2.1.8: http://take.ms/Cp62g

[orlangur]

Looks like there was a copy-paste typo in 77ac45b. While 'up for grabs' is usually used for some huge necessary changes, would be nice to have some label like https://github.com/facebook/hhvm/issues?q=is%3Aopen+is%3Aissue+label%3A%22probably+easy%22 for smaller issues.

[magento-engcom-team]

@korostii @ekuusela We always encourage you to submit a Pull Request if the fix is that easy.
Otherwise clear issue report is required, so that developer working can precisely identify issue and possible testing scenarios.
Thank you for understanding.

[korostii]

@magento-engcom-team I think you're missing the point.
The issue was clearly valid and had just the right amount of information on it.
If it has plenty info for a PR (BTW thank you @Zifius for coming forward #11134 ), it should be enough of a "clear issue report".

Dismissing the issue after manual review with a comment that's clearly hostile (I mean, caps? http://take.ms/MWYka was that really necessary? ) because the formatting is not to your liking isn't an okay way to greet voluntary bug reports.

Don't we have a Code of Conduct which says that everyone should be, and I quote: "Gracefully accepting constructive criticism" and "Focusing on what is best for the community"?
IMHO that comment goes a little overboard with this urge to get the issue template right.

[ishakhsuvarov]

I have to lock this conversation as it is now beyond

"Gracefully accepting constructive criticism"

Thanks for collaboration. Fix for the issue hopefully will be delivered with the next patch for 2.2.

[magento-engcom-team]

Hi @irinikp the issue has been fixed in 2.2.1 and will be available soon (#11134)

[magento-team]

Internal ticket to track issue progress: MAGETWO-80515

[magento-team]

Hi @irinikp. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1282 by @magento-engcom-team in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming patch release.