Hi Thomas, I appreciate your reply. Now I clearly understand how the spdy-proxy configuration works. There was some points I misunderstood.
Thanks a lot! On Tue, Nov 27, 2012 at 3:58 AM, Thomas Becker <[email protected]> wrote: > Hi Daehyeok, > > I just retested the default config and it works just fine. However I don't > think that our spdy-proxy will fit your use case. Have a closer look at > jetty-spdy-proxy.xml which provides a reverse-proxy and not a > forward-proxy. It's used to translate incoming HTTP, SPDYv2 and SPDYv3 > requests to a local nonssl SPDYv3 connector. You can use it as well to > terminate SPDY at your frontend and forward requests as plain HTTP to your > backend (in case you have a network component that needs to look at plain > http, your backend is not capable of talking SPDY, etc.). > > It won't work as a forward-proxy. Could you please describe your use case > and what you think you'll gain using SPDY? > > Cheers, > Thomas > > Am 11/26/12 11:53 PM, schrieb Daehyeok Kim: > > Hi Thomas, > > Thanks for the reply. > I downloaded M3 and tested with jetty-spdy-proxy.xml. > But, it still doesn't work. In jetty-spdy-proxy I commented out > unnecessary things in start.ini. And in jetty-spdy-proxy.xml, only thing I > modified is changing proxyEngineSelector part with my own SPDY proxy's > information. I checked whether my proxy works well again. > > I ran the jetty with jetty-spdy-proxy.xml and set the browser's proxy > setting to 127.0.0.1 : 8080. The browser cannot get fetch anything. > > Could you check whether it works and my configuration is correct? > > Thank you. > > > On Mon, Nov 26, 2012 at 11:07 AM, Thomas Becker <[email protected]>wrote: > >> Hi DK, >> >> sorry, for the late reply. I've verified the config last week and it was >> a bit outdated. We fixed that already. I will retry the config tomorrow to >> verify it really works. >> >> You can also try M3 yourself as the config should work fine in M3 again. >> Please let us know if it worked for you, because then I don't need to try >> it myself tomorrow. >> >> Cheers, >> Thomas >> >> Am 11/19/12 4:36 PM, schrieb D.K.: >> >>> Hi all, >>> >>> >>> I tried to run jetty server with jetty-spdy-proxy.xml configuration. >>> I am using the latest version of jetty (stable 9.0.0 M2). >>> It seems that there is no method named *defaultConnectionFactory* in >>> HTTPSPDYServerConnector class. >>> When I run a server, this error occurs: >>> >>> Caused by: java.lang.NoSuchMethodException: class >>> org.eclipse.jetty.spdy.server. >>> http.HTTPSPDYServerConnector.setDefaultConnectionFactory(class >>> java.lang.Object) >>> >>> Has anyone tried to run jetty server with jetty-spdy-proxy.xml in 9.0.0 >>> M2 >>> version? >>> >>> Thank you. >>> >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://jetty.4.n6.nabble.com/jetty-spdy-proxy-xml-doesn-t-work-tp4959577.html >>> Sent from the Jetty User mailing list archive at Nabble.com. >>> _______________________________________________ >>> jetty-users mailing list >>> [email protected] >>> https://dev.eclipse.org/mailman/listinfo/jetty-users >>> >> >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > > > _______________________________________________ > jetty-users mailing > [email protected]https://dev.eclipse.org/mailman/listinfo/jetty-users > > > > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
