Skip to content

[WIP] Fix Server Name Indication (SNI) issues on legacy PHP < 5.6 - #66

Closed
clue wants to merge 1 commit into
reactphp-legacy:masterfrom
clue-labs:sni
Closed

[WIP] Fix Server Name Indication (SNI) issues on legacy PHP < 5.6#66
clue wants to merge 1 commit into
reactphp-legacy:masterfrom
clue-labs:sni

Conversation

@clue

@clueclue commented Apr 13, 2016

Copy link
Copy Markdown
Contributor

Looks like #43 introduced some issues with SNI hosts, which means that both v0.5.0 and v0.4.5 are broken. I stumbled upon this while trying to issue HTTPS requests against a host that requires proper SNI support.

This ticket aims to document this issue, add required tests cases and ultimately fix this.

@clueclue added the bug label Apr 13, 2016
@clueclue added this to the v0.5.1 milestone Apr 13, 2016
@clue

clue commented May 18, 2016

Copy link
Copy Markdown
ContributorAuthor

@clueclue modified the milestones: v0.5.1, v0.6.0Nov 15, 2016
@clueclue changed the title [WIP] Fix Server Name Indication (SNI) issues[WIP] Fix Server Name Indication (SNI) issues on legacy PHP < 5.6Jan 10, 2017
@clue

clue commented Feb 16, 2017

Copy link
Copy Markdown
ContributorAuthor

This will be postponed for a future release. See #83 instead

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@clue