Implement support for h2c.

ari-ban / issue-test

0 stars 0 forks source link

Implement support for h2c. #1858

Closed arinban closed 8 years ago

arinban commented 8 years ago

Per the summary. There may be use cases h2c is preferred when communication between end points is on a private network.

arinban commented 6 years ago

Issue Imported From: https://github.com/javaee/grizzly/issues/1858
Original Issue Raised By:@glassfishrobot
Original Issue Assigned To:@rlubke
Original Issue Closed By:@glassfishrobot

arinban commented 8 years ago

@glassfishrobot Commented Reported by @rlubke

arinban commented 8 years ago

@glassfishrobot Commented @rlubke said: Verified that h2c is supported within the current code base using the HTTP Upgrade mechanism.

Need to verify that it's possible for a client to send the preface instead of using Upgrade to eliminate a round-trip.

arinban commented 8 years ago

@glassfishrobot Commented @rlubke said: Okay, so h2c connections without using HTTP Upgrade are supported, however, the headers aren't being parsed properly.

I've updated the hpac implementation which seems to have resolved it.

arinban commented 8 years ago

@glassfishrobot Commented @rlubke said: Next step is to add tests for http2 support without Upgrades.

arinban commented 8 years ago

@glassfishrobot Commented @rlubke said: Changes to support h2c connection without HTTP/.1. upgrade: 7ed3104c711dea30fcc386fd643ced2cf6acc6b2

arinban commented 8 years ago

@glassfishrobot Commented Parent-Task: GRIZZLY-1542

arinban commented 7 years ago

@glassfishrobot Commented This issue was imported from java.net JIRA GRIZZLY-1858

arinban commented 8 years ago

@glassfishrobot Commented Marked as fixed on Monday, August 15th 2016, 3:17:20 pm