Credentialed CORS: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Give the endpoint purpose, origin matcher and credentials setting. Compare an exact allowlist with broad reflected origins and missing policy details.
CORS concerns which browser origins may read a cross-origin response. With credentialed responses, unrestricted origin reflection is different from an exact allowlist of intended application origins.
A literal wildcard combined with credentials is also different from reflecting an arbitrary concrete origin. Browsers reject the wildcard combination for credentialed reads; the example treats it as a configuration needing review, not proof of successful access.
The linked linter checks credentialed-origin trust. This exercise does not send cross-origin requests. Authentication, CSRF protection, cookie attributes and server permissions remain separate controls.
This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Use the sample to understand the rule, then test your own input for credentialed cors.

Give the endpoint purpose, origin matcher and credentials setting.

Open the decision rules and keep the intended distinction between Exact policy, Broad trust, Public noncredentialed, Review. Edit the choices only when testing your own rule.

Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

Review Review before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Exact allowlist | Exact policy | 96.0% |
| Reflect any origin | Broad trust | 77.0% |
| Weak substring matcher | Broad trust | 80.0% |
| Public data endpoint | Public noncredentialed | 99.0% |
| Unknown origin callback | Review | 88.0% |
| Literal wildcard with credentials | Review | 81.0% |
These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json
# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.The input contract and these limits define what the result means.
Not as a literal Access-Control-Allow-Origin: * response. Browsers reject that combination for credentialed reads. Reflecting arbitrary concrete origins is a different configuration.
The scheme, hostname and port matter. This example supplies an explicit parsed exact-origin policy rather than relying on a substring of a URL.
It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.
No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.
Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.