Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correctly update cached addresses for accepted Channels. #98

Merged
merged 1 commit into from
Mar 5, 2018

Conversation

normanmaurer
Copy link
Member

Motivation:

We missed to correctly update the cached remote and local addresses for accepted Channels. Because of this localAddress and remoteAddr always returned nil.

Modifications:

  • Update cached addresses when constructing SocketChannel from existing Socket.
  • Add testcase

Result:

Fixes [#97].

Motivation:

We missed to correctly update the cached remote and local addresses for accepted Channels. Because of this localAddress and remoteAddr always returned nil.

Modifications:

- Update cached addresses when constructing SocketChannel from existing Socket.
- Add testcase

Result:

Fixes [apple#97].
@normanmaurer
Copy link
Member Author

Also @ezfe

@normanmaurer normanmaurer self-assigned this Mar 4, 2018
@normanmaurer normanmaurer added bug Something isn't working patch-version-bump-only For PRs that when merged will only cause a bump of the patch version, ie. 1.0.x -> 1.0.(x+1) labels Mar 4, 2018
Copy link
Contributor

@Lukasa Lukasa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, good catch, that's a definite miss. LGTM.

@Lukasa Lukasa merged commit f3d3267 into apple:master Mar 5, 2018
@normanmaurer normanmaurer added this to the 1.1.0 milestone Mar 5, 2018
@normanmaurer normanmaurer deleted the accepted_channel_addr branch April 23, 2018 12:08
weissi pushed a commit to weissi/swift-nio that referenced this pull request Jun 13, 2020
Motivation:

RFC 7540 requires that compliant specifications emit errors if content-length has been incorrectly
set. We should have this behaviour by default, though we should allow it to be disabled if necessary.

Modifications:

- Added content-length checking.
- Added flag to disable content-length checking.

Result:

Better RFC 7540 compliance.
weissi pushed a commit to weissi/swift-nio that referenced this pull request Feb 3, 2024
Motivation:

It's useful to know the overhead we could be adding by including
the PCAP handler.

Modifications:

Add a new executable based on the NIO performance testing executable.

Result:

There is a new executable which runs a short test of sending and receiving
data through the HTTP/1 handler using multiple eventloops and showing
three options.
1) Vanilla
2) With in memory PCAP never written to disk
3) With a disk based PCAP.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working patch-version-bump-only For PRs that when merged will only cause a bump of the patch version, ie. 1.0.x -> 1.0.(x+1)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants