This pull request will resolve the following open issues on the sectxt repo.
Note that does not verify the signature #34
Check for Line Separator? #21
What message when security.txt file is NOT available via https? #24
The changes also includes
more detailed gitignore
pytest and request mock in the requirements
more tests, some including not just the parser but also the initial domain checks
In regards to issue #34: I agree that there might be some misconception since it is a validator of security.txt. A index is added to the signature recommendation which clarifies this.
In regards to issue #21: The RFC does specify that every line MUST end using a line feed. An error for this is added, which checks if the final line is an empty line. If this is not the case not all lines end with a line feed.
In regards to issue: #24: In the event that the security.txt is hosted but not on https it would give an error that it could not find it. This might cause confusion, since the file is hosted. An additional check is added which checks the insecure URI scheme. If the security.txt is found than an error is added which clarifies that the scheme is not correct and the https scheme should be used.
This pull request will resolve the following open issues on the sectxt repo.
The changes also includes
In regards to issue #34: I agree that there might be some misconception since it is a validator of security.txt. A index is added to the signature recommendation which clarifies this. In regards to issue #21: The RFC does specify that every line MUST end using a line feed. An error for this is added, which checks if the final line is an empty line. If this is not the case not all lines end with a line feed. In regards to issue: #24: In the event that the security.txt is hosted but not on https it would give an error that it could not find it. This might cause confusion, since the file is hosted. An additional check is added which checks the insecure URI scheme. If the security.txt is found than an error is added which clarifies that the scheme is not correct and the https scheme should be used.