Hi luke Have you resolved this issue? I also found this error.
Thanks. 在 2016年4月15日星期五 UTC+8下午5:10:08，[email protected]写道： > > I changed it to this > > ByteBuf payload = unreleasableBuffer(copiedBuffer(poststring, > CharsetUtil.UTF_8)); > http2responseHandler.encoder().writeFrame(ctx, Http2FrameTypes.HEADERS, > streamId, new Http2Flags().priorityPresent(true) , payload, > ctx.newPromise()); > > Now i recive > > ----------------OUTBOUND-------------------- > [id: 0x1b3be271, L:/127.0.0.1:3152 - R:/127.0.0.1:8443] UNKNOWN: > frameType=1, streamId=5, flags=32, length=46, bytes=7b2 > > 022616374696f6e223a20226368616e6e656c5f666f725f70757368222c202273747265616d4964223a20357d > > What means UNKNOWN: there Should be HEADERS ... > > > > > Am Freitag, 15. April 2016 10:56:14 UTC+2 schrieb [email protected]: >> >> Now i am able to call the encoder from my main method >> >> Http2ResponseHandler http2responseHandler = >> initializer.http2responseHandler(); >> >> http2responseHandler.encoder().writeFrame(ChannelHandlerContext ctx, byte >> frameType, int streamId, Http2Flags flags, ByteBuf payload, ChannelPromise >> promise) >> >> now i have the question about the ChannelHandlerContext. I have non in >> my main method. So where to create it?`because its needed to do the >> request... >> >> Am Donnerstag, 14. April 2016 11:15:13 UTC+2 schrieb Julien Viet: >>> >>> I think you can post questions in this forum and people can reply, I >>> will reply if I’m available and I can help you, otherwise others might as >>> well! >>> >>> On Apr 14, 2016, at 11:13 AM, [email protected] wrote: >>> >>> Thank you. Can i answer you for further questions? >>> >>> Am Donnerstag, 14. April 2016 11:04:18 UTC+2 schrieb Julien Viet: >>>> >>>> yes. >>>> >>>> you make requests using the encoder . >>>> >>>> you receive responses with the frame listener . >>>> >>>> On Apr 14, 2016, at 11:00 AM, [email protected] wrote: >>>> >>>> Okay, >>>> >>>> i will try to set up the client on HTTP2. >>>> >>>> I am using netty 4.1 RC7 btw. >>>> >>>> A problem i figured out earlier was that the import static >>>> io.netty.handler.codec.http.HttpVersion.HTTP_1_1; is the highest Version i >>>> find. So i was not able to send GET or POST Requests over HTTP2.... >>>> >>>> So i have to set up a connection? And then i can sent POST / GETS via >>>> frames and streams manually? >>>> >>>> >>>> >>>> Am Donnerstag, 14. April 2016 10:53:12 UTC+2 schrieb Julien Viet: >>>>> >>>>> of course! >>>>> >>>>> but client/server api are really similar once you get the >>>>> HTTP2Connection and the codec. >>>>> >>>>> you should first focus on setting up an Http2Connection in the client >>>>> using the Http2ConnectionBuilder and then after register your frame >>>>> listener >>>>> >>>>> On Apr 14, 2016, at 10:44 AM, [email protected] wrote: >>>>> >>>>> I thought that the 1.1 upgrade lets the Client Server Communication >>>>> run over HTTP/2 Api :/ >>>>> >>>>> So i have to write a Client in HTTP/2 to use the HTTP/2 API. This is >>>>> possible in netty? >>>>> >>>>> Am Donnerstag, 14. April 2016 10:40:15 UTC+2 schrieb Julien Viet: >>>>>> >>>>>> actually no, I was right. >>>>>> >>>>>> this example does not use the HTTP/2 api and instead the HTTP/1.1 >>>>>> codec : >>>>>> >>>>>> Process {@link io.netty.handler.codec.http.FullHttpResponse} >>>>>> translated from HTTP/2 frames >>>>>> >>>>>> so you need to look elsewhere. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Apr 14, 2016, at 10:36 AM, Julien Viet <[email protected]> >>>>>> wrote: >>>>>> >>>>>> actually what I said is stupid :-), HTTP/1.1 is used for the Upgrade >>>>>> >>>>>> let me look >>>>>> >>>>>> On Apr 14, 2016, at 10:35 AM, Julien Viet <[email protected]> >>>>>> wrote: >>>>>> >>>>>> this client uses an adapter of HTTP/1.1 on top of HTTP/2 so there is >>>>>> no way to do it this way. >>>>>> >>>>>> On Apr 14, 2016, at 10:31 AM, [email protected] wrote: >>>>>> >>>>>> I have a problem to find the right place to add the >>>>>> Http2FrameListenere on netty http2 client example ( >>>>>> https://github.com/netty/netty/tree/4.1/example/src/main/java/io/netty/example/http2/helloworld/client >>>>>> ) >>>>>> >>>>>> You may have a hint for me? >>>>>> >>>>>> Regards and thank you! >>>>>> >>>>>> Am Donnerstag, 14. April 2016 10:08:35 UTC+2 schrieb lukeju...@ >>>>>> gmail.com: >>>>>>> >>>>>>> Ok, can't I use a Class extends Http2ConnectionHandler implements >>>>>>> Http2FrameListener to handle PUSH_PROMISES? >>>>>>> >>>>>>> Am Donnerstag, 14. April 2016 10:04:37 UTC+2 schrieb Julien Viet: >>>>>>>> >>>>>>>> it needs to be registered against the Http2ConnectionDecoder >>>>>>>> >>>>>>>> On Apr 14, 2016, at 9:48 AM, [email protected] wrote: >>>>>>>> >>>>>>>> Thank you again. Can I simply add the Http2FrameListener to the >>>>>>>> Client Pipeline? >>>>>>>> >>>>>>>> Am Donnerstag, 14. April 2016 09:26:20 UTC+2 schrieb Julien Viet: >>>>>>>>> >>>>>>>>> you need to handle the push promise with the Http2FrameListener >>>>>>>>> onPushPromiseRead and I think then there is nothing else special to >>>>>>>>> do >>>>>>>>> except receive the headers / data frames for this new stream. >>>>>>>>> >>>>>>>>> On Apr 14, 2016, at 9:24 AM, [email protected] wrote: >>>>>>>>> >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> after my Server now is able to send PUSH_PROMISE Frames. I try to >>>>>>>>> push resources to the client. Therefore i want to know: How do i have >>>>>>>>> to >>>>>>>>> handle the PUSH_PROMISE on the Client. For now the Client answers >>>>>>>>> automaticly with a GO_AWAY Frame. >>>>>>>>> >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Luke >>>>>>>>> >>>>>>>>> -- >>>>>>>>> You received this message because you are subscribed to the Google >>>>>>>>> Groups "Netty discussions" group. >>>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>>> send an email to [email protected]. >>>>>>>>> To view this discussion on the web visit >>>>>>>>> https://groups.google.com/d/msgid/netty/eea5a347-fe94-4dcc-8ac5-d0a63cb863c0%40googlegroups.com >>>>>>>>> >>>>>>>>> <https://groups.google.com/d/msgid/netty/eea5a347-fe94-4dcc-8ac5-d0a63cb863c0%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>> . >>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "Netty discussions" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>> send an email to [email protected]. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/netty/5be20d82-71f1-4023-93bb-35a32173e193%40googlegroups.com >>>>>>>> >>>>>>>> <https://groups.google.com/d/msgid/netty/5be20d82-71f1-4023-93bb-35a32173e193%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Netty discussions" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/netty/9c768044-724a-4dc5-bfe6-86d56d627cf2%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/netty/9c768044-724a-4dc5-bfe6-86d56d627cf2%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Netty discussions" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/netty/2702bb84-1a16-493a-886f-2ccd17e6b411%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/netty/2702bb84-1a16-493a-886f-2ccd17e6b411%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Netty discussions" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/netty/28111af4-5064-4801-8706-3ced8c2ceb4e%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/netty/28111af4-5064-4801-8706-3ced8c2ceb4e%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Netty discussions" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/netty/4b273801-fa47-4951-8d6f-4b9cda84eb80%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/netty/4b273801-fa47-4951-8d6f-4b9cda84eb80%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/8ade2b2e-f57c-4848-acde-19f994fd51bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
