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.

Sign up for GitHub

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

Jump to bottom

document HTTP/S guidance #38

Open
caindy opened this issue Jan 25, 2024 · 0 comments
Open

document HTTP/S guidance #38

caindy opened this issue Jan 25, 2024 · 0 comments
Labels
Task catch-all for tasks not associated with spec changes
Milestone
Documentation

Comments

@caindy
Copy link
Contributor

caindy commented Jan 25, 2024

Using the "MUST" and "SHOULD" language, document guidance for clients and server implementations. As an example:

"Clients SHOULD send a custom User-Agent header that identifies the client software by name and version. Servers SHOULD consider the use of firewalls rules that detect and block generic / scripting clients."
@caindy caindy added the Task catch-all for tasks not associated with spec changes label Jun 22, 2024
@catkins-miso catkins-miso added this to the Documentation milestone Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Task catch-all for tasks not associated with spec changes
Projects
TROLIE 1.0
Status: No status
Milestone
Documentation
Development

No branches or pull requests
2 participants
@caindy @catkins-miso