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

Check that WebFinger tests test for the correct HTTP status codes, and fix annost #61

Closed
jernst opened this issue May 5, 2024 · 1 comment
Closed

Check that WebFinger tests test for the correct HTTP status codes, and fix annost #61

jernst opened this issue May 5, 2024 · 1 comment
Assignees
@jernst
Milestone
Webfinger tests p...

Comments

@jernst
Copy link
Member

jernst commented May 5, 2024

Right now we don't have traceability between the HTTP status codes we check in the WebFinger tests, and where in the RFC those are specified. Add that connection, and fix HTTP status codes if needed. (It may be via section 4.2 where particular status codes are specified via RFC 2616.)
@jernst jernst self-assigned this May 5, 2024
@jernst jernst mentioned this issue May 5, 2024
Merged
@jernst jernst added this to the Webfinger tests published milestone May 16, 2024
@jernst
Copy link
Member Author

jernst commented May 29, 2024

I think we are done with this.

@jernst jernst closed this as completed May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jernst jernst

Labels
None yet
Projects
None yet
Milestone
Webfinger tests published
Development

No branches or pull requests
1 participant
@jernst