Skip to content

Use standard return code and content-type#20

Merged
vkhoroz merged 1 commit intofoundriesio:mainfrom
orangepizza:standard-types
Feb 13, 2026
Merged

Use standard return code and content-type#20
vkhoroz merged 1 commit intofoundriesio:mainfrom
orangepizza:standard-types

Conversation

@orangepizza
Copy link
Contributor

RFC7030 4.2.3 requires return code 200 and content type with smime-type certs-only parameter. Old versions of fioconfig-clients have wrong expectations, so added check to mimic old behavior.

Signed-off-by: Seo Suchan tjtncks@gmail.com

fixes #19

@doanac doanac requested a review from vkhoroz February 12, 2026 14:24
Copy link
Member

@vkhoroz vkhoroz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the commit @orangepizza .

I think we should be functionally fine; only need to cleanup the comments and tests.

@orangepizza orangepizza force-pushed the standard-types branch 3 times, most recently from a92c7b9 to d38a498 Compare February 12, 2026 18:02
RFC7030 4.2.3 requires return code 200 and content type with smime-type certs-only parameter.
Old versions of fioconfig-clients have wrong expectations, so added check to mimic old behavior
for old client

Signed-off-by: Seo Suchan <tjtncks@gmail.com>
Copy link
Member

@vkhoroz vkhoroz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

All checks and tests passed locally for me.

@doanac Do you want to give it a shot?

I will merge it tomorrow if you don't mind.

@vkhoroz vkhoroz merged commit 8395135 into foundriesio:main Feb 13, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Server sending out-of spec response for enroll/reenroll

2 participants

Comments