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

CMSD header compliance/validator reference example #17

Open
kevleyski opened this issue May 19, 2022 · 4 comments
Open

CMSD header compliance/validator reference example #17

kevleyski opened this issue May 19, 2022 · 4 comments

Comments

@kevleyski
Copy link

Would be good to include a reference that validates the CMSD data

Spec is moving around a bit, but an online validator and maybe some open source code would be good as a reference

@kevleyski
Copy link
Author

As a Rust engineer more than happy to contribute some super slim parser/validator library (libcmsd crate maybe)

Though what in reality is useful for testing?

Something you can proxy pass to via nginx/Apache for example?
Web site form copy and paste Charlse proxy data maybe at it picks out the issues
Wireshark module, etc...

@wilaw
Copy link
Contributor

wilaw commented May 19, 2022

I think a simple page based script might be useful, with two modes of operation:

  1. You enter a URL. The test page makes a GET request and then parses and validate any CMSD headers it receives in the response.
  2. You have a form field in which someone can paste a set of headers, such as are obtained by the browser network panels, or charles proxy HAR etc. The script would then parse and validate the received CMSD information.

@wilaw
Copy link
Contributor

wilaw commented Oct 17, 2022

@kevleyski - checking in on this. Any progress/interest on a validation concept, now that spec is in TWG review?

@kevleyski
Copy link
Author

kevleyski commented Oct 17, 2022 via email

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

No branches or pull requests

2 participants