Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refined search #509

Open
Malvoz opened this issue Sep 9, 2018 · 1 comment
Open

Refined search #509

Malvoz opened this issue Sep 9, 2018 · 1 comment

Comments

@Malvoz
Copy link
Member

Malvoz commented Sep 9, 2018

Initially I was wondering if Expect-CT should apply to all responses (if served over HTTPS) and not only text/html responses, so I used the search bar and found nothing.

Then to try out the search capabilities I searched for x-frame-options and that entire list shows links to documentation on x-content-type-options, however as I used the webhint-scanner earlier I know that x-frame-options is considered in the checks so it was just a matter of actually finding the documentation on it.

It'd be helpful if there could be improvements in this area, having the webhint.io scanner telling you that you did something wrong and how to fix it is great, amazing in fact! But being able to find documentation beforehand during development would be too.

@molant
Copy link
Member

molant commented Sep 10, 2018

Thanks for your feedback @Malvoz!

You are right, we should do better in this area. We are using algolia and basically use the defaults of the service for indexing and showing results. We should look into the documentation to see what can be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants