Ticket #871 (enhancement)
Opened 1 year ago
Last modified 6 months ago
Turn off ipv6only on systems where it is on by default
Status: closed (fixed)
| Reported by: | martin@v.loewis.de | Assigned to: | fumanchu |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.1 |
| Component: | CherryPy code | Keywords: | |
| Cc: |
Systems vary in their treatment of the IPV6_V6ONLY option; the RFC says it should be on by default (apparently, only Linux deviates). For CherryPy, I propose that it is more useful if the default is off, when the user specifies :: as the bind_address - this supposedly means "all incoming connections". The attached patch makes sure the option is disabled on systems that have the option in the first place.
Attachments
Change History
11/02/08 14:01:56: Modified by martin@v.loewis.de
- attachment v6only.diff added.
11/08/08 15:52:49: Modified by fumanchu
- status changed from new to closed.
- resolution set to fixed.
- milestone set to 3.1.
06/22/09 10:01:10: Modified by mihai.ibanescu@yahoo.com
- status changed from closed to reopened.
- resolution deleted.
You have applied the patch at the wrong level. Manipulating the IPV6 stack should happen regardless of whether or not one has passed in SSL certificate files. Martin's patch was doing that at the same level as self.socket.bind(), while now it is done with an additional indent.
08/05/09 00:03:21: Modified by fumanchu
- status changed from reopened to closed.
- resolution set to fixed.
Fixed in [2098].
Applied in [2076] (by mistake with a bunch of test fixes, but OK).