issues
search
w3c
/
baggage
Propagation format for distributed context: Baggage
https://w3c.github.io/baggage/
Other
46
stars
18
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Clarify how compliant implementations should handle invalid baggage entries
#137
lachmatt
opened
1 month ago
2
Implementation report and CR tweaks
#136
plehegar
closed
1 month ago
0
Clarification regarding baggage list-member value
#135
lachmatt
opened
1 month ago
0
Extend parse tests with more use cases
#134
pellared
opened
3 months ago
0
Add notes explaining missing unicode character support
#133
dyladan
closed
2 months ago
0
Remove all markdown includes
#132
dyladan
closed
1 month ago
0
Test harness to show handling of invalid inputs
#131
yurishkuro
opened
3 months ago
0
Use the term code point where character may be ambiguous
#130
dyladan
closed
3 months ago
0
Update the Status of the document
#129
plehegar
closed
4 months ago
0
We need to document the reasoning for the supported character range
#128
kalyanaj
closed
2 months ago
0
Baggage: Mention about minimum limits approach first before describing the conditions
#127
kalyanaj
closed
4 months ago
1
When multiple baggage headers are used, clarify that minimum limits apply to the cumulative total
#126
kalyanaj
closed
4 months ago
3
Percent character in value MUST be percent-encoded
#125
pellared
closed
5 months ago
5
Precent character in value must be precent-encoded
#124
pellared
closed
5 months ago
0
chore: add acknowledgments
#123
basti1302
closed
11 months ago
0
Acknowledgements
#122
basti1302
closed
11 months ago
5
Don't merge
#121
plehegar
closed
3 months ago
1
Allow unicode in baggage keys by referencing XML
#120
dyladan
closed
4 months ago
2
Run tests on pull requests
#119
dyladan
closed
1 year ago
0
update editors
#118
basti1302
closed
1 year ago
0
Initial unicode baggage keys
#117
dyladan
closed
1 year ago
2
DO NOT MERGE
#116
plehegar
closed
1 year ago
2
Clarification on how baggage should be propagated when using websockets
#115
mediocregopher
closed
1 year ago
2
Update rationale with text that applies to lower limits
#114
dyladan
closed
1 year ago
0
Clarify what happens when limits are violated
#113
dyladan
closed
1 year ago
1
Need to update the limits section in rationale to be in sync with the new lower limits
#112
kalyanaj
closed
1 year ago
1
Add note that applications using baggage must be aware that data can be propagated to other systems
#111
kalyanaj
closed
1 year ago
11
Specify Relationship to other HTTP Header encoding proposals.
#110
kalyanaj
closed
1 year ago
0
Provide clarification for how this specification is different from TraceContext.
#109
kalyanaj
closed
1 year ago
0
Make trust/privacy boundary explicit (at least in browsers)
#107
pes10k
closed
1 year ago
0
Relationship to other HTTP Header encoding proposals
#106
pes10k
closed
1 year ago
8
Clarify in text the relationship to Trace Context
#105
pes10k
closed
1 year ago
1
RFC 8941
#104
martinthomson
closed
1 year ago
2
ReSpec fix
#103
xfq
closed
2 years ago
0
Add example of percent-encoding non-ASCII characters in value field of a baggage list member
#102
kalyanaj
closed
2 years ago
0
Resolves #100 (UTF-8 encoding of value should be more clearly defined).
#101
kalyanaj
closed
2 years ago
1
UTF-8 encoding of value should be more clearly defined
#100
aphillips
closed
2 years ago
0
Keys don't permit non-ASCII?
#99
aphillips
closed
4 months ago
20
no non-ASCII examples
#98
aphillips
closed
2 years ago
0
Updated title to reflect that this specification is for distributed context
#97
kalyanaj
closed
2 years ago
3
Spec title should not mention "tracing"
#96
yurishkuro
closed
1 year ago
1
Self-Review Questionnaire: Security and Privacy
#95
kalyanaj
closed
1 year ago
2
Self-review for accessibility
#94
kalyanaj
closed
2 years ago
1
Clarify Baggage Propagation Limits
#108
dpauls
closed
1 year ago
1
i18n review checklist for baggage
#93
kalyanaj
closed
1 year ago
3
Define RFC for percent-encoding
#92
dyladan
closed
2 years ago
0
Wide review
#91
plehegar
closed
2 months ago
5
chore: use group shortnames
#90
plehegar
closed
2 years ago
0
Define lower bounds for header limits
#89
dyladan
closed
2 years ago
2
Use a more descriptive sentence instead of "opaque"
#88
dyladan
closed
2 years ago
1
Next