Testing only a legacy security.txt does not refresh

[janwillemstegink]

In addition to the fix in #1510:
https://en.internet.nl/site/metaregistrar.com/3182102/ says

'The file must be published under the /.well-known/ path. Note that placing it under the top-level path has been deprecated. Every web (sub) domain should have its own security.txt file. An example file can be found on https://example.nl/.well-known/security.txt.'

Compare https://www.hostingtool.nl/server_headers/index.php?url=metaregistrar.com

[WKobes]

Hi @janwillemstegink, I do not understand the issue, what do you mean with 'does not refresh'?

[janwillemstegink]

It is about:

'The file must be published under the /.well-known/ path. Note that placing it under the top-level path has been deprecated. Every web (sub) domain should have its own security.txt file. An example file can be found on https://example.nl/.well-known/security.txt.'

The remark should I think only be shown if applicable. Now it is shown in every situation.

[WKobes]

Ah, right, this is part of the test explanation and will be shown irregardless of the test result.

[janwillemstegink]

Currently the text is correct if warning:
Error: security.txt was located on the top-level path (legacy place), but must be placed under the '/.well-known/' path.

I read the text below explaining for the almost deprecated situation, as reporting an error in setup to note and fix:
'The file must be published under the /.well-known/ path. Note that placing it under the top-level path has been deprecated. Every web (sub) domain should have its own security.txt file. An example file can be found on https://example.nl/.well-known/security.txt.'