Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / w3c/baggage issues and pull requests
#128 - We need to document the reasoning for the supported character range
Issue -
State: open - Opened by kalyanaj about 1 year ago
#127 - Baggage: Mention about minimum limits approach first before describing the conditions
Issue -
State: closed - Opened by kalyanaj about 1 year ago
- 1 comment
#126 - When multiple baggage headers are used, clarify that minimum limits apply to the cumulative total
Issue -
State: closed - Opened by kalyanaj about 1 year ago
- 3 comments
#125 - Percent character in value MUST be percent-encoded
Pull Request -
State: closed - Opened by pellared about 1 year ago
- 5 comments
#124 - Precent character in value must be precent-encoded
Issue -
State: closed - Opened by pellared about 1 year ago
#123 - chore: add acknowledgments
Pull Request -
State: closed - Opened by basti1302 over 1 year ago
#122 - Acknowledgements
Issue -
State: closed - Opened by basti1302 over 1 year ago
- 5 comments
#121 - Don't merge
Pull Request -
State: open - Opened by plehegar over 1 year ago
#120 - Allow unicode in baggage keys by referencing XML
Pull Request -
State: open - Opened by dyladan almost 2 years ago
- 1 comment
#119 - Run tests on pull requests
Pull Request -
State: closed - Opened by dyladan almost 2 years ago
#118 - update editors
Pull Request -
State: closed - Opened by basti1302 almost 2 years ago
#117 - Initial unicode baggage keys
Pull Request -
State: closed - Opened by dyladan almost 2 years ago
- 2 comments
#116 - DO NOT MERGE
Pull Request -
State: closed - Opened by plehegar almost 2 years ago
- 2 comments
#115 - Clarification on how baggage should be propagated when using websockets
Issue -
State: closed - Opened by mediocregopher over 2 years ago
- 2 comments
#114 - Update rationale with text that applies to lower limits
Pull Request -
State: closed - Opened by dyladan over 2 years ago
#113 - Clarify what happens when limits are violated
Pull Request -
State: closed - Opened by dyladan over 2 years ago
- 1 comment
#112 - Need to update the limits section in rationale to be in sync with the new lower limits
Issue -
State: closed - Opened by kalyanaj over 2 years ago
- 1 comment
#111 - Add note that applications using baggage must be aware that data can be propagated to other systems
Pull Request -
State: closed - Opened by kalyanaj over 2 years ago
- 11 comments
#110 - Specify Relationship to other HTTP Header encoding proposals.
Pull Request -
State: closed - Opened by kalyanaj over 2 years ago
#109 - Provide clarification for how this specification is different from TraceContext.
Pull Request -
State: closed - Opened by kalyanaj over 2 years ago
#108 - Clarify Baggage Propagation Limits
Issue -
State: closed - Opened by dpauls almost 3 years ago
- 1 comment
#107 - Make trust/privacy boundary explicit (at least in browsers)
Issue -
State: closed - Opened by pes10k over 2 years ago
Labels: privacy-needs-resolution
#106 - Relationship to other HTTP Header encoding proposals
Issue -
State: closed - Opened by pes10k over 2 years ago
- 8 comments
Labels: privacy-tracker
#105 - Clarify in text the relationship to Trace Context
Issue -
State: closed - Opened by pes10k over 2 years ago
- 1 comment
Labels: privacy-needs-resolution
#104 - RFC 8941
Issue -
State: closed - Opened by martinthomson over 2 years ago
- 2 comments
#103 - ReSpec fix
Pull Request -
State: closed - Opened by xfq over 2 years ago
#102 - Add example of percent-encoding non-ASCII characters in value field of a baggage list member
Pull Request -
State: closed - Opened by kalyanaj over 2 years ago
#101 - Resolves #100 (UTF-8 encoding of value should be more clearly defined).
Pull Request -
State: closed - Opened by kalyanaj over 2 years ago
- 1 comment
#100 - UTF-8 encoding of value should be more clearly defined
Issue -
State: closed - Opened by aphillips over 2 years ago
Labels: i18n-needs-resolution
#99 - Keys don't permit non-ASCII?
Issue -
State: closed - Opened by aphillips over 2 years ago
- 20 comments
Labels: i18n-needs-resolution
#98 - no non-ASCII examples
Issue -
State: closed - Opened by aphillips over 2 years ago
Labels: i18n-needs-resolution
#97 - Updated title to reflect that this specification is for distributed context
Pull Request -
State: closed - Opened by kalyanaj almost 3 years ago
- 3 comments
#96 - Spec title should not mention "tracing"
Issue -
State: closed - Opened by yurishkuro almost 3 years ago
- 1 comment
#95 - Self-Review Questionnaire: Security and Privacy
Issue -
State: closed - Opened by kalyanaj almost 3 years ago
- 2 comments
#94 - Self-review for accessibility
Issue -
State: closed - Opened by kalyanaj almost 3 years ago
- 1 comment
#93 - i18n review checklist for baggage
Issue -
State: closed - Opened by kalyanaj almost 3 years ago
- 3 comments
Labels: w3c, i18n-tracker
#92 - Define RFC for percent-encoding
Pull Request -
State: closed - Opened by dyladan almost 3 years ago
#91 - Wide review
Issue -
State: open - Opened by plehegar almost 3 years ago
- 4 comments
Labels: w3c
#90 - chore: use group shortnames
Pull Request -
State: closed - Opened by plehegar almost 3 years ago
Labels: w3c
#89 - Define lower bounds for header limits
Pull Request -
State: closed - Opened by dyladan almost 3 years ago
- 2 comments
#88 - Use a more descriptive sentence instead of "opaque"
Pull Request -
State: closed - Opened by dyladan almost 3 years ago
- 1 comment
#87 - Remove unenforceable requirement to strip whitespace
Pull Request -
State: closed - Opened by dyladan almost 3 years ago
- 1 comment
#86 - Create a baggage reference implementation
Pull Request -
State: closed - Opened by dyladan almost 3 years ago
- 3 comments
#84 - Different behaviour in private browsing/incognito mode?
Issue -
State: closed - Opened by hadleybeeman about 3 years ago
- 2 comments
#83 - Name 'baggage' is a metaphor and could be hard for non-native English speakers
Issue -
State: closed - Opened by hadleybeeman about 3 years ago
- 3 comments
#82 - Clarify what implementations should do when baggage length is exceeded or when invalid entry is found
Pull Request -
State: closed - Opened by kalyanaj about 3 years ago
#81 - Reference the relevant RFC for URL encoding baggage values
Issue -
State: closed - Opened by kalyanaj about 3 years ago
- 1 comment
#80 - Update baggage specification to clarify expectation when length is exceeded or when invalid entry is found
Issue -
State: closed - Opened by kalyanaj about 3 years ago
#79 - Use RFC 7230 for token definition
Pull Request -
State: closed - Opened by dyladan about 3 years ago
- 1 comment
#78 - Apply url encoding to single header example, matching multiple
Pull Request -
State: closed - Opened by anuraaga over 3 years ago
- 2 comments
#77 - Baggage value clarification for parsing
Issue -
State: closed - Opened by srikanthccv over 3 years ago
- 1 comment
#76 - Move Daniel Khan to former editors
Pull Request -
State: closed - Opened by dyladan over 3 years ago
#75 - Publish FPWD
Issue -
State: closed - Opened by SergeyKanzhelev over 3 years ago
- 4 comments
#74 - Create a test as a reference implementation
Issue -
State: closed - Opened by kalyanaj over 3 years ago
- 3 comments
#73 - Add auto-publish.yml
Pull Request -
State: closed - Opened by plehegar over 3 years ago
#72 - Move non-format information to overview and expand
Pull Request -
State: closed - Opened by dyladan over 3 years ago
- 1 comment
#71 - Replace references to "traces" with "distributed request".
Pull Request -
State: closed - Opened by kalyanaj over 3 years ago
#70 - Add few use cases for baggage.
Pull Request -
State: closed - Opened by kalyanaj over 3 years ago
#69 - Added information about reference implementations of the baggage specification
Pull Request -
State: closed - Opened by kalyanaj over 3 years ago
#68 - Add information about reference implementations to README.
Issue -
State: closed - Opened by kalyanaj over 3 years ago
#67 - Add section about baggage mutations
Pull Request -
State: closed - Opened by dyladan over 3 years ago
#66 - Add a security section
Pull Request -
State: closed - Opened by dyladan over 3 years ago
- 1 comment
#65 - Consider lowering baggage limits
Issue -
State: closed - Opened by dyladan over 3 years ago
- 4 comments
#64 - Remove arbitrary cookie rationale
Pull Request -
State: closed - Opened by dyladan over 3 years ago
#63 - Switch this specification to auto-publishing
Issue -
State: closed - Opened by plehegar over 3 years ago
- 1 comment
Labels: w3c
#62 - Update editors to reflect current contributors
Pull Request -
State: closed - Opened by danielkhan over 3 years ago
#61 - a few small fixes
Pull Request -
State: closed - Opened by SergeyKanzhelev over 3 years ago
#60 - Rename master branch to main
Issue -
State: closed - Opened by plehegar almost 4 years ago
- 3 comments
Labels: w3c
#59 - Fix the path to privacy.md
Pull Request -
State: closed - Opened by SergeyKanzhelev almost 4 years ago
#58 - Requirement to strip OWS out of scope
Issue -
State: closed - Opened by dyladan almost 4 years ago
- 6 comments
#57 - Extend ABNF to allow multi-octet values
Pull Request -
State: closed - Opened by dyladan almost 4 years ago
#56 - Current ABNF only allows for single-character baggage value
Issue -
State: closed - Opened by dyladan almost 4 years ago
#55 - Clarify whether length is in bytes or characters
Issue -
State: open - Opened by SergeyKanzhelev almost 4 years ago
- 4 comments
Labels: i18n-tracker
#54 - Remove optional whitespace
Pull Request -
State: closed - Opened by dyladan almost 4 years ago
- 1 comment
#53 - Remove optional whitespace
Issue -
State: closed - Opened by dyladan almost 4 years ago
- 6 comments
#52 - Clarify ABNF limits
Pull Request -
State: closed - Opened by dyladan almost 4 years ago
#51 - Do name-value pair limits include the equals sign?
Issue -
State: closed - Opened by anuraaga almost 4 years ago
- 1 comment
#50 - Add section about Mutating baggage
Pull Request -
State: closed - Opened by danielkhan almost 4 years ago
- 1 comment
#49 - Adds a Privacy section
Pull Request -
State: closed - Opened by danielkhan almost 4 years ago
#48 - fix #25: remove inconsistency
Pull Request -
State: closed - Opened by SergeyKanzhelev almost 4 years ago
#47 - Add security section
Pull Request -
State: closed - Opened by danielkhan almost 4 years ago
- 1 comment
#46 - fix #34: note, that equal sign can be used in the value
Pull Request -
State: closed - Opened by SergeyKanzhelev almost 4 years ago
#45 - small cleanup
Pull Request -
State: closed - Opened by SergeyKanzhelev over 4 years ago
#44 - respec update
Pull Request -
State: closed - Opened by caribouW3 over 4 years ago
#42 - Grammar nits
Pull Request -
State: closed - Opened by mtwo over 4 years ago
#40 - Update Editors
Issue -
State: closed - Opened by mtwo over 4 years ago
#36 - CfC: Move to First Public Working Draft
Issue -
State: closed - Opened by danielkhan over 4 years ago
- 5 comments
#34 - Clarify if values are allowed to contain `=`
Issue -
State: closed - Opened by arminru over 4 years ago
- 2 comments
Labels: workshop-fall-2020
#33 - Simplify grammar for list-member
Pull Request -
State: closed - Opened by arminru over 4 years ago
- 3 comments
#32 - Fix section hierarchy
Pull Request -
State: closed - Opened by arminru over 4 years ago
#31 - Fix syntax definition syntax and references
Pull Request -
State: closed - Opened by arminru over 4 years ago
- 1 comment
#30 - limitations do not appear to have standard implementation for enforcement
Issue -
State: closed - Opened by dmikey over 4 years ago
- 13 comments
Labels: workshop-fall-2020
#28 - Do not refer to "traces" in the baggage spec
Issue -
State: closed - Opened by danielkhan over 4 years ago
Labels: workshop-fall-2020
#26 - Review / update rationale
Issue -
State: closed - Opened by danielkhan over 4 years ago
- 1 comment
Labels: workshop-fall-2020
#25 - Add rationale for why libraries MAY propagate or otherwise change to MUST
Issue -
State: closed - Opened by anuraaga almost 5 years ago
- 6 comments
Labels: workshop-fall-2020
#22 - revert arbitrary "cookie" rationale
Issue -
State: closed - Opened by codefromthecrypt almost 5 years ago
- 4 comments
Labels: workshop-fall-2020
#21 - remove Latest published version header
Issue -
State: closed - Opened by samuelweiler almost 5 years ago
- 1 comment
#16 - OpenTelemetry and Correlation Context
Issue -
State: closed - Opened by mwear about 5 years ago
- 8 comments
#12 - Security and encryption considerations
Issue -
State: closed - Opened by remitly-srivatsa over 5 years ago
- 2 comments
Labels: workshop-fall-2020
#11 - Clarify distinction between correlation-context and trace-context's tracestate
Issue -
State: closed - Opened by iredelmeier over 5 years ago
- 2 comments
Labels: workshop-fall-2020