- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 16 Mar 2021 17:00:45 +0000
- To: public-trace-context@w3.org
- Message-Id: <E1lMD3l-0001rj-EX@uranus.w3.org>
Issues ------ * w3c/trace-context (+0/-4/💬1) 1 issues received 1 new comments: - #438 How to preserve trace context on http redirect ? (1 by danielkhan) https://github.com/w3c/trace-context/issues/438 4 issues closed: - Clarify use of trace-id in response header https://github.com/w3c/trace-context/issues/407 [workshop-fall-2020] - How to preserve trace context on http redirect ? https://github.com/w3c/trace-context/issues/438 - Should a tracestate key always be allowed to start with a lowercase letter or digit? https://github.com/w3c/trace-context/issues/441 - Move response header Returning the traceresponse Field to non-normative processing section. https://github.com/w3c/trace-context/issues/445 Pull requests ------------- * w3c/trace-context (+0/-1/💬0) 1 pull requests merged: - Move traceresponse processing to processing model https://github.com/w3c/trace-context/pull/450 Repositories tracked by this digest: ----------------------------------- * https://github.com/w3c/trace-context * https://github.com/w3c/correlation-context * https://github.com/w3c/distributed-tracing-wg -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 March 2021 17:00:47 UTC