Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / martinthomson/http-replay issues and pull requests

#43 - Early data that arrives after the handshake completes

Issue - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#43 - Early data that arrives after the handshake completes

Issue - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#42 - I'm sure that this was just Ben playing a prank

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#42 - I'm sure that this was just Ben playing a prank

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#41 - Don't repeat TLS advice

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#41 - Don't repeat TLS advice

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#40 - Fix a few nits

Pull Request - State: closed - Opened by kaduk over 7 years ago - 1 comment

#40 - Fix a few nits

Pull Request - State: closed - Opened by kaduk over 7 years ago - 1 comment

#39 - track mandatory server anti-replay measures

Issue - State: closed - Opened by kaduk over 7 years ago

#39 - track mandatory server anti-replay measures

Issue - State: closed - Opened by kaduk over 7 years ago

#38 - Acknowledge some people

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#38 - Acknowledge some people

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#37 - Pick a status code

Issue - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#37 - Pick a status code

Issue - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#36 - Add denial of service considerations

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 9 comments

#36 - Add denial of service considerations

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 9 comments

#35 - Add TLS implementation requirements

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 2 comments

#35 - Add TLS implementation requirements

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 2 comments

#34 - There are some things that are safe to do

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#34 - There are some things that are safe to do

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#33 - Servers can't delay if Early-Data is present

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 3 comments

#33 - Servers can't delay if Early-Data is present

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 3 comments

#32 - Intermediaries can retry

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 5 comments

#32 - Intermediaries can retry

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 5 comments

#31 - 425 (Too Early)

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 3 comments

#31 - 425 (Too Early)

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 3 comments

#30 - Awareness matters

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 2 comments

#30 - Awareness matters

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 2 comments

#29 - Let the intermediary retry

Issue - State: closed - Opened by martinthomson over 7 years ago - 5 comments

#28 - Add short overview section describing the basic model

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 2 comments

#28 - Add short overview section describing the basic model

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 2 comments

#27 - Save the 'be consistent' text

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 6 comments

#27 - Save the 'be consistent' text

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 6 comments

#26 - Acknowledge some people

Issue - State: closed - Opened by martinthomson over 7 years ago

#26 - Acknowledge some people

Issue - State: closed - Opened by martinthomson over 7 years ago

#25 - Make the client use Early-Data

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 5 comments

#25 - Make the client use Early-Data

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 5 comments

#24 - Improve security considerations

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#24 - Improve security considerations

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#23 - Allow the intermediary to generate 4NN (Too Early)

Issue - State: closed - Opened by martinthomson over 7 years ago - 3 comments

#23 - Allow the intermediary to generate 4NN (Too Early)

Issue - State: closed - Opened by martinthomson over 7 years ago - 3 comments

#22 - Just another reminder that you don't have to enable 0-RTT

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 3 comments

#22 - Just another reminder that you don't have to enable 0-RTT

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 3 comments

#21 - If the gateway isn't sure that the origin supports Early-Data

Issue - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#21 - If the gateway isn't sure that the origin supports Early-Data

Issue - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#20 - Add text on 0.5 RTT

Issue - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#20 - Add text on 0.5 RTT

Issue - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#19 - On requests that are only partially in 0-RTT

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 2 comments

#19 - On requests that are only partially in 0-RTT

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 2 comments

#18 - On side effects

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#18 - On side effects

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#17 - The effect of generic anti-replay

Pull Request - State: closed - Opened by martinthomson over 7 years ago

#17 - The effect of generic anti-replay

Pull Request - State: closed - Opened by martinthomson over 7 years ago

#16 - Talk about requests that span 0-RTT and 1-RTT

Issue - State: closed - Opened by martinthomson over 7 years ago - 4 comments

#16 - Talk about requests that span 0-RTT and 1-RTT

Issue - State: closed - Opened by martinthomson over 7 years ago - 4 comments

#15 - two minor adjustments (0-RTT and "might have been")

Pull Request - State: closed - Opened by wtarreau over 7 years ago - 2 comments

#15 - two minor adjustments (0-RTT and "might have been")

Pull Request - State: closed - Opened by wtarreau over 7 years ago - 2 comments

#14 - Tweaks

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 2 comments

#14 - Tweaks

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 2 comments

#13 - Stuff II

Pull Request - State: closed - Opened by mnot over 7 years ago - 3 comments

#13 - Stuff II

Pull Request - State: closed - Opened by mnot over 7 years ago - 3 comments

#12 - Shall we ship this thing?

Issue - State: closed - Opened by martinthomson over 7 years ago - 29 comments

#11 - A more thorough explanation of the replay attack enabled by retrying

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 1 comment

#10 - Don't assume

Pull Request - State: closed - Opened by martinthomson over 7 years ago

#9 - Infer support by client

Pull Request - State: closed - Opened by martinthomson over 7 years ago - 3 comments

#8 - mostly editorial stuff

Pull Request - State: closed - Opened by wtarreau over 7 years ago - 4 comments

#7 - servers must not generate 422 without early data header field

Issue - State: closed - Opened by wtarreau over 7 years ago - 3 comments

#6 - risk of getting multiple early-data header fields

Issue - State: closed - Opened by wtarreau over 7 years ago - 6 comments

#5 - risks for the client

Issue - State: closed - Opened by wtarreau over 7 years ago - 2 comments

#4 - Unclear explanation

Issue - State: closed - Opened by wtarreau over 7 years ago

#3 - So, I kind of ended up rewriting it...

Pull Request - State: closed - Opened by mnot over 7 years ago - 6 comments

#2 - Scope

Issue - State: closed - Opened by mnot over 7 years ago - 2 comments

#1 - Too Soon?

Issue - State: closed - Opened by martinthomson over 7 years ago - 11 comments