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

Support html content type #34

Open
1 of 6 tasks
danielemery opened this issue Aug 1, 2024 · 0 comments
Open
1 of 6 tasks

Support html content type #34

danielemery opened this issue Aug 1, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@danielemery
Copy link
Owner

danielemery commented Aug 1, 2024

Currently the main keys endpoint returns keys in a format that is suitable for use in an authorized_keys file without any parsing or modification.
This is a key features of the keys project and should be kept as the default behaviour.

However if the caller requests content-type: html they should instead receive the content in html. This will be a lot easier to view in the browser and can later support features like automatically copying keys to clipboard and clicking on tags to filter by them etc.

Attention should be given to still keeping the container as light as possible.

This issue can be completed in the following parts to help keep PRs small:

  • Force content-type to plain when a file extension is provided
  • Return html for the home page when requested
  • Return html for the ssh key list when requested
  • Return html for the pgp list when requested
  • Return html for individual pgp key when requested
  • Return html for known hosts when requested
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant