Menu
▾
▴
webassembletool-users — ESIGate user list
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
(1) |
Feb
|
Mar
(6) |
Apr
(1) |
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
(8) |
Nov
|
Dec
(1) |
| 2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(9) |
Jun
(2) |
Jul
(5) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2014 |
Jan
(1) |
Feb
|
Mar
|
Apr
(7) |
May
(6) |
Jun
(7) |
Jul
|
Aug
|
Sep
(5) |
Oct
(29) |
Nov
(14) |
Dec
(10) |
| 2015 |
Jan
|
Feb
(4) |
Mar
(8) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
(6) |
Nov
|
Dec
(2) |
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(21) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: alexis t. <ale...@gm...> - 2014-10-28 10:21:02
|
Bonjour, Je viens de placer le code du prototype sur github https://github.com/alexist/esigate-portlet La portlet permet d'intégrer un block par provider, et ne gère pas l'authentification. Vous trouverez un peu de doc sur le README du projet N'hésitez pas à me contacter si vous rencontrez des problèmes. Le 23 octobre 2014 11:44, Ahmed Drira <ahm...@gm...> a écrit : > Bonjour > Merci Romain , j'ai déjà consulter les deux articles et c'est pour ça que > j'ai choisie esigate ; > > @philippe est ce que je peut bénéficier de votre retour d'expérience avec ce > POC > > > Le 23 octobre 2014 10:19, Philippe De Oliveira > <phi...@gm...> a écrit : > >> Bonjour, >> >> Oui c'est possible, j'ai fais un PoC exactement comme ça il y a moins d'un >> an et ça fonctionne. >> >> Cordialement, >> >> 2014-10-22 22:00 GMT+02:00 Ahmed Drira <ahm...@gm...>: >>> >>> Bonjour >>> est ce que possible de faire appel à esigate + esi:include pour intégrer >>> une application tiers dans ma portail à travers une portlet >>> bien sûre après avoir ajouter le filtre dans le web.xml de mon portlet et >>> ajouter esigate-core et esigate-servlet avec mes jar >>> >>> Bien cordialement >>> -- >>> Ahmed DRIRA >>> Computer engineer >>> S.A.R.L. Alpha Engineering - Tunisia >>> Résidence El Habib, Bloc 3 - Bureaux 33 & 34 >>> 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis >>> | URL : www.alpha-engineering.net >>> | Mob : 55 61 47 88 >>> | Te : 71 96 49 06 >>> | Fax : 71 96 41 53 >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Webassembletool-users mailing list >>> Web...@li... >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>> >> >> >> >> -- >> Philippe De Oliveira >> > > > > -- > Ahmed DRIRA > Computer engineer > S.A.R.L. Alpha Engineering - Tunisia > Résidence El Habib, Bloc 3 - Bureaux 33 & 34 > 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis > | URL : www.alpha-engineering.net > | Mob : 55 61 47 88 > | Te : 71 96 49 06 > | Fax : 71 96 41 53 > > ------------------------------------------------------------------------------ > > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > |
|
From: alexis t. <ale...@gm...> - 2014-10-26 21:20:06
|
Hi, The documentation has been updated on 5.0-SNAPSHOT version ( http://www.esigate.org/5.0-SNAPSHOT ) 2014-10-24 16:33 GMT+02:00 Volker Kümmer <vol...@gm...>: > just want to let you know, that with the esigate server my wicket > application is working (just one problem, that should be possible to solve). > So it seems that the proxyservlet is doing something different, as with the > filter my application is not working. > > just 2 little notes: > - it would be helpful to correct the quickstart > (http://www.esigate.org/quickstart.html) and add there the "s" to the > mapping configuration, too > - its just cosmetic, but it would be nice, if the description line for 302 > would be "Found", not "Temporary redirect" > > thanks for the help and pointers I've gotten here! > > 2014-10-24 14:16 GMT+02:00 Francois-Xavier Bonnet > <fra...@ce...>: >> >> Can you try with "esigate.mappings" (with a "s")? >> >> 24 окт. 2014 г. 12:55 пользователь "Volker Kümmer" >> <vol...@gm...> написал: >>> >>> >you should try esigate as a standalone proxy (esigate-server or >>> > esigate-war). >>> >>> unfortunately I am not able to get esigate server working. It seems to be >>> any easy installation, but if I use this configuration >>> >>> esigate.remoteUrlBase=http://localhost:8080/ >>> esigate.mapping=/* >>> >>> and this command for starting >>> >>> java -Desigate.config=esigate.properties -Dserver.port=8082 -jar >>> esigate-server-5.0-SNAPSHOT.jar start >>> >>> I only get "No mapping defined for this url." when calling >>> http://localhost:8082/ >>> >>> Am I doing something wrong? >>> >>> 2014-10-16 9:08 GMT+02:00 Nicolas Richeton <nic...@gm...>: >>>> >>>> Hi Volker, >>>> >>>> The proxy filter is a new addition to esigate 5.0. >>>> Your feedback is really valuable to catch the last bugs before the >>>> stable release, but if you want something that just work, you should try >>>> esigate as a standalone proxy (esigate-server or esigate-war). >>>> >>>> We have several applications using esigate + wicket in production with >>>> no issue. >>>> >>>> -- >>>> Nicolas >>>> >>>> Le 15 oct. 2014 à 18:02, Volker Kümmer <vol...@gm...> a >>>> écrit : >>>> >>>> hi >>>> >>>> good to know, that it should work in principle. >>>> >>>> I had not enough time, to really debug the problems, to see where it >>>> originated from. >>>> >>>> But in the moment I am having two problems. >>>> >>>> 1. when the proxy filter is not in front of the wicket application, if I >>>> send a redirect after a post, I get es 302 redirect. But when the ESIGate >>>> proxy filter is in front of the application I will get an 307 redirect -- I >>>> do not know why in the moment. >>>> >>>> 2. when using the wicket ajax mechanisms I will always get an error -- >>>> it works without any problems without the proxy filter: >>>> >>>> java.lang.IllegalStateException: WRITER >>>> at org.mortbay.jetty.Response.getOutputStream(Response.java:564) >>>> at >>>> org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) >>>> at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) >>>> at >>>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) >>>> at >>>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) >>>> at >>>> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) >>>> at >>>> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) >>>> at >>>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) >>>> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) >>>> at >>>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) >>>> at org.mortbay.jetty.Server.handle(Server.java:295) >>>> at >>>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) >>>> at >>>> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) >>>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) >>>> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) >>>> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) >>>> at >>>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) >>>> at >>>> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) >>>> >>>> >>>> I am not using any esi or caching functionality. I have just configured >>>> the proxyfilter before the application. I will see, if I can get some more >>>> detailed information. >>>> >>>> >>>> >>>> 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet >>>> <fra...@ce...>: >>>>> >>>>> Hi Volker, >>>>> >>>>> The beta-1 versions is currently being tested on a few projects. Since >>>>> this version, we have made a few improvements or bug fixes but no blocking >>>>> issue. >>>>> Usually we release a new beta version every time we find a blocking >>>>> issue that need a fix and the stable release comes when a major project >>>>> using EsiGate is ready to go to production. >>>>> >>>>> I would be very interested in having more information about the errors >>>>> you have. If a beta-2 is required, we could release it very quickly. >>>>> >>>>> 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: >>>>>> >>>>>> Hello >>>>>> >>>>>> I would like to know, what the current state of ESIGate is? >>>>>> >>>>>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get >>>>>> ESIGate configured, so that it served some content. >>>>>> >>>>>> But now I get some errors. I have ESIGate in front of a wicket >>>>>> application and there are some problems with it. So I would like to know, >>>>>> whether there are some speciel configurations neccessary to get it working >>>>>> or if the beta-1 from february 2014 is simply outdated, >>>>>> >>>>>> In the moment my application runs behind ESIGate, but I have not set >>>>>> any caching headers up to now. So I expected that the application would work >>>>>> as without ESIGate. >>>>>> >>>>>> If it should work with the beta-1 I will further investigate the >>>>>> problem. But in the moment I just would like to know, if (these) problems >>>>>> are to be expected, as it is still a beta. >>>>>> >>>>>> kind regards >>>>>> Volker >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS >>>>>> Reports >>>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>>>>> http://p.sf.net/sfu/Zoho >>>>>> _______________________________________________ >>>>>> Webassembletool-users mailing list >>>>>> Web...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>>>>> >>>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Comprehensive Server Monitoring with Site24x7. >>>> Monitor 10 servers for $9/Month. >>>> Get alerted through email, SMS, voice calls or mobile push >>>> notifications. >>>> Take corrective actions from your mobile device. >>>> http://p.sf.net/sfu/Zoho >>>> >>>> _______________________________________________ >>>> Webassembletool-users mailing list >>>> Web...@li... >>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Webassembletool-users mailing list >>> Web...@li... >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > |
|
From: Volker K. <vol...@gm...> - 2014-10-24 14:33:18
|
just want to let you know, that with the esigate server my wicket application is working (just one problem, that should be possible to solve). So it seems that the proxyservlet is doing something different, as with the filter my application is not working. just 2 little notes: - it would be helpful to correct the quickstart ( http://www.esigate.org/quickstart.html) and add there the "s" to the mapping configuration, too - its just cosmetic, but it would be nice, if the description line for 302 would be "Found", not "Temporary redirect" thanks for the help and pointers I've gotten here! 2014-10-24 14:16 GMT+02:00 Francois-Xavier Bonnet < fra...@ce...>: > Can you try with "esigate.mappings" (with a "s")? > 24 окт. 2014 г. 12:55 пользователь "Volker Kümmer" < > vol...@gm...> написал: > >> >you should try esigate as a standalone proxy (esigate-server or >> esigate-war). >> >> unfortunately I am not able to get esigate server working. It seems to be >> any easy installation, but if I use this configuration >> >> esigate.remoteUrlBase=http://localhost:8080/ >> esigate.mapping=/* >> >> and this command for starting >> >> java -Desigate.config=esigate.properties -Dserver.port=8082 -jar >> esigate-server-5.0-SNAPSHOT.jar start >> >> I only get "No mapping defined for this url." when calling >> http://localhost:8082/ >> >> Am I doing something wrong? >> >> 2014-10-16 9:08 GMT+02:00 Nicolas Richeton <nic...@gm...>: >> >>> Hi Volker, >>> >>> The proxy filter is a new addition to esigate 5.0. >>> Your feedback is really valuable to catch the last bugs before the >>> stable release, but if you want something that just work, you should try >>> esigate as a standalone proxy (esigate-server or esigate-war). >>> >>> We have several applications using esigate + wicket in production with >>> no issue. >>> >>> -- >>> Nicolas >>> >>> Le 15 oct. 2014 à 18:02, Volker Kümmer <vol...@gm...> a >>> écrit : >>> >>> hi >>> >>> good to know, that it should work in principle. >>> >>> I had not enough time, to really debug the problems, to see where it >>> originated from. >>> >>> But in the moment I am having two problems. >>> >>> 1. when the proxy filter is not in front of the wicket application, if I >>> send a redirect after a post, I get es 302 redirect. But when the ESIGate >>> proxy filter is in front of the application I will get an 307 redirect -- I >>> do not know why in the moment. >>> >>> 2. when using the wicket ajax mechanisms I will always get an error -- >>> it works without any problems without the proxy filter: >>> >>> java.lang.IllegalStateException: WRITER >>> at org.mortbay.jetty.Response.getOutputStream(Response.java:564) >>> at >>> org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) >>> at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) >>> at >>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) >>> at >>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) >>> at >>> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) >>> at >>> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) >>> at >>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) >>> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) >>> at >>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) >>> at org.mortbay.jetty.Server.handle(Server.java:295) >>> at >>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) >>> at >>> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) >>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) >>> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) >>> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) >>> at >>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) >>> at >>> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) >>> >>> >>> I am not using any esi or caching functionality. I have just configured >>> the proxyfilter before the application. I will see, if I can get some more >>> detailed information. >>> >>> >>> >>> 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet < >>> fra...@ce...>: >>> >>>> Hi Volker, >>>> >>>> The beta-1 versions is currently being tested on a few projects. Since >>>> this version, we have made a few improvements or bug fixes but no blocking >>>> issue. >>>> Usually we release a new beta version every time we find a blocking >>>> issue that need a fix and the stable release comes when a major project >>>> using EsiGate is ready to go to production. >>>> >>>> I would be very interested in having more information about the errors >>>> you have. If a beta-2 is required, we could release it very quickly. >>>> >>>> 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: >>>> >>>>> Hello >>>>> >>>>> I would like to know, what the current state of ESIGate is? >>>>> >>>>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get >>>>> ESIGate configured, so that it served some content. >>>>> >>>>> But now I get some errors. I have ESIGate in front of a wicket >>>>> application and there are some problems with it. So I would like to know, >>>>> whether there are some speciel configurations neccessary to get it working >>>>> or if the beta-1 from february 2014 is simply outdated, >>>>> >>>>> In the moment my application runs behind ESIGate, but I have not set >>>>> any caching headers up to now. So I expected that the application would >>>>> work as without ESIGate. >>>>> >>>>> If it should work with the beta-1 I will further investigate the >>>>> problem. But in the moment I just would like to know, if (these) problems >>>>> are to be expected, as it is still a beta. >>>>> >>>>> kind regards >>>>> Volker >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS >>>>> Reports >>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>>>> http://p.sf.net/sfu/Zoho >>>>> _______________________________________________ >>>>> Webassembletool-users mailing list >>>>> Web...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>>>> >>>>> >>>> >>> >>> ------------------------------------------------------------------------------ >>> Comprehensive Server Monitoring with Site24x7. >>> Monitor 10 servers for $9/Month. >>> Get alerted through email, SMS, voice calls or mobile push notifications. >>> Take corrective actions from your mobile device. >>> http://p.sf.net/sfu/Zoho >>> >>> _______________________________________________ >>> Webassembletool-users mailing list >>> Web...@li... >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>> >>> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Webassembletool-users mailing list >> Web...@li... >> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-10-24 12:16:43
|
Can you try with "esigate.mappings" (with a "s")? 24 окт. 2014 г. 12:55 пользователь "Volker Kümmer" <vol...@gm...> написал: > >you should try esigate as a standalone proxy (esigate-server or > esigate-war). > > unfortunately I am not able to get esigate server working. It seems to be > any easy installation, but if I use this configuration > > esigate.remoteUrlBase=http://localhost:8080/ > esigate.mapping=/* > > and this command for starting > > java -Desigate.config=esigate.properties -Dserver.port=8082 -jar > esigate-server-5.0-SNAPSHOT.jar start > > I only get "No mapping defined for this url." when calling > http://localhost:8082/ > > Am I doing something wrong? > > 2014-10-16 9:08 GMT+02:00 Nicolas Richeton <nic...@gm...>: > >> Hi Volker, >> >> The proxy filter is a new addition to esigate 5.0. >> Your feedback is really valuable to catch the last bugs before the stable >> release, but if you want something that just work, you should try esigate >> as a standalone proxy (esigate-server or esigate-war). >> >> We have several applications using esigate + wicket in production with no >> issue. >> >> -- >> Nicolas >> >> Le 15 oct. 2014 à 18:02, Volker Kümmer <vol...@gm...> a >> écrit : >> >> hi >> >> good to know, that it should work in principle. >> >> I had not enough time, to really debug the problems, to see where it >> originated from. >> >> But in the moment I am having two problems. >> >> 1. when the proxy filter is not in front of the wicket application, if I >> send a redirect after a post, I get es 302 redirect. But when the ESIGate >> proxy filter is in front of the application I will get an 307 redirect -- I >> do not know why in the moment. >> >> 2. when using the wicket ajax mechanisms I will always get an error -- it >> works without any problems without the proxy filter: >> >> java.lang.IllegalStateException: WRITER >> at org.mortbay.jetty.Response.getOutputStream(Response.java:564) >> at >> org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) >> at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) >> at >> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) >> at >> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) >> at >> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) >> at >> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) >> at >> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) >> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) >> at >> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) >> at org.mortbay.jetty.Server.handle(Server.java:295) >> at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) >> at >> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) >> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) >> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) >> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) >> at >> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) >> at >> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) >> >> >> I am not using any esi or caching functionality. I have just configured >> the proxyfilter before the application. I will see, if I can get some more >> detailed information. >> >> >> >> 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet < >> fra...@ce...>: >> >>> Hi Volker, >>> >>> The beta-1 versions is currently being tested on a few projects. Since >>> this version, we have made a few improvements or bug fixes but no blocking >>> issue. >>> Usually we release a new beta version every time we find a blocking >>> issue that need a fix and the stable release comes when a major project >>> using EsiGate is ready to go to production. >>> >>> I would be very interested in having more information about the errors >>> you have. If a beta-2 is required, we could release it very quickly. >>> >>> 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: >>> >>>> Hello >>>> >>>> I would like to know, what the current state of ESIGate is? >>>> >>>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get >>>> ESIGate configured, so that it served some content. >>>> >>>> But now I get some errors. I have ESIGate in front of a wicket >>>> application and there are some problems with it. So I would like to know, >>>> whether there are some speciel configurations neccessary to get it working >>>> or if the beta-1 from february 2014 is simply outdated, >>>> >>>> In the moment my application runs behind ESIGate, but I have not set >>>> any caching headers up to now. So I expected that the application would >>>> work as without ESIGate. >>>> >>>> If it should work with the beta-1 I will further investigate the >>>> problem. But in the moment I just would like to know, if (these) problems >>>> are to be expected, as it is still a beta. >>>> >>>> kind regards >>>> Volker >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>>> http://p.sf.net/sfu/Zoho >>>> _______________________________________________ >>>> Webassembletool-users mailing list >>>> Web...@li... >>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>>> >>>> >>> >> >> ------------------------------------------------------------------------------ >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> http://p.sf.net/sfu/Zoho >> >> _______________________________________________ >> Webassembletool-users mailing list >> Web...@li... >> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
|
From: Volker K. <vol...@gm...> - 2014-10-24 10:55:04
|
>you should try esigate as a standalone proxy (esigate-server or esigate-war). unfortunately I am not able to get esigate server working. It seems to be any easy installation, but if I use this configuration esigate.remoteUrlBase=http://localhost:8080/ esigate.mapping=/* and this command for starting java -Desigate.config=esigate.properties -Dserver.port=8082 -jar esigate-server-5.0-SNAPSHOT.jar start I only get "No mapping defined for this url." when calling http://localhost:8082/ Am I doing something wrong? 2014-10-16 9:08 GMT+02:00 Nicolas Richeton <nic...@gm...>: > Hi Volker, > > The proxy filter is a new addition to esigate 5.0. > Your feedback is really valuable to catch the last bugs before the stable > release, but if you want something that just work, you should try esigate > as a standalone proxy (esigate-server or esigate-war). > > We have several applications using esigate + wicket in production with no > issue. > > -- > Nicolas > > Le 15 oct. 2014 à 18:02, Volker Kümmer <vol...@gm...> a > écrit : > > hi > > good to know, that it should work in principle. > > I had not enough time, to really debug the problems, to see where it > originated from. > > But in the moment I am having two problems. > > 1. when the proxy filter is not in front of the wicket application, if I > send a redirect after a post, I get es 302 redirect. But when the ESIGate > proxy filter is in front of the application I will get an 307 redirect -- I > do not know why in the moment. > > 2. when using the wicket ajax mechanisms I will always get an error -- it > works without any problems without the proxy filter: > > java.lang.IllegalStateException: WRITER > at org.mortbay.jetty.Response.getOutputStream(Response.java:564) > at > org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) > at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) > at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) > at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) > at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) > at org.mortbay.jetty.Server.handle(Server.java:295) > at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) > at > org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) > at > org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) > > > I am not using any esi or caching functionality. I have just configured > the proxyfilter before the application. I will see, if I can get some more > detailed information. > > > > 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet < > fra...@ce...>: > >> Hi Volker, >> >> The beta-1 versions is currently being tested on a few projects. Since >> this version, we have made a few improvements or bug fixes but no blocking >> issue. >> Usually we release a new beta version every time we find a blocking issue >> that need a fix and the stable release comes when a major project using >> EsiGate is ready to go to production. >> >> I would be very interested in having more information about the errors >> you have. If a beta-2 is required, we could release it very quickly. >> >> 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: >> >>> Hello >>> >>> I would like to know, what the current state of ESIGate is? >>> >>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get >>> ESIGate configured, so that it served some content. >>> >>> But now I get some errors. I have ESIGate in front of a wicket >>> application and there are some problems with it. So I would like to know, >>> whether there are some speciel configurations neccessary to get it working >>> or if the beta-1 from february 2014 is simply outdated, >>> >>> In the moment my application runs behind ESIGate, but I have not set any >>> caching headers up to now. So I expected that the application would work as >>> without ESIGate. >>> >>> If it should work with the beta-1 I will further investigate the >>> problem. But in the moment I just would like to know, if (these) problems >>> are to be expected, as it is still a beta. >>> >>> kind regards >>> Volker >>> >>> >>> ------------------------------------------------------------------------------ >>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>> http://p.sf.net/sfu/Zoho >>> _______________________________________________ >>> Webassembletool-users mailing list >>> Web...@li... >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>> >>> >> > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
|
From: Romain <as...@gm...> - 2014-10-23 09:47:20
|
Yop, Alexis avait travaillé sur ce sujet il y a peu. Quelques traces sur le net : - http://blog.smile.fr/Integrer-metier-et-liferay-avec-esi-gate-partie-1-2 - http://blog.smile.fr/Integrer-metier-et-liferay-avec-esi-gate-partie-2-2 Je ne sais pas s'il est prévu que Smile ouvre ses sources ou non ... Si ce projet passe en opensource, il serait d'ailleurs peut être bon d'en parler sur ce post de forum : - https://www.liferay.com/community/forums/-/message_boards/message/40195522 (l'ancien projet sur google code n'est plus d'actualité). __ Romain Le 23 oct. 2014 à 11:19, Philippe De Oliveira <phi...@gm...> a écrit : > Bonjour, > > Oui c'est possible, j'ai fais un PoC exactement comme ça il y a moins d'un an et ça fonctionne. > > Cordialement, > > 2014-10-22 22:00 GMT+02:00 Ahmed Drira <ahm...@gm...>: > Bonjour > est ce que possible de faire appel à esigate + esi:include pour intégrer une application tiers dans ma portail à travers une portlet > bien sûre après avoir ajouter le filtre dans le web.xml de mon portlet et ajouter esigate-core et esigate-servlet avec mes jar > > Bien cordialement > -- > Ahmed DRIRA > Computer engineer > S.A.R.L. Alpha Engineering - Tunisia > Résidence El Habib, Bloc 3 - Bureaux 33 & 34 > 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis > | URL : www.alpha-engineering.net > | Mob : 55 61 47 88 > | Te : 71 96 49 06 > | Fax : 71 96 41 53 > > ------------------------------------------------------------------------------ > > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > > > > -- > Philippe De Oliveira > > ------------------------------------------------------------------------------ > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users |
|
From: Ahmed D. <ahm...@gm...> - 2014-10-23 09:44:44
|
Bonjour Merci Romain , j'ai déjà consulter les deux articles et c'est pour ça que j'ai choisie esigate ; @philippe est ce que je peut bénéficier de votre retour d'expérience avec ce POC Le 23 octobre 2014 10:19, Philippe De Oliveira < phi...@gm...> a écrit : > Bonjour, > > Oui c'est possible, j'ai fais un PoC exactement comme ça il y a moins d'un > an et ça fonctionne. > > Cordialement, > > 2014-10-22 22:00 GMT+02:00 Ahmed Drira <ahm...@gm...>: > >> Bonjour >> est ce que possible de faire appel à esigate + esi:include pour intégrer >> une application tiers dans ma portail à travers une portlet >> bien sûre après avoir ajouter le filtre dans le web.xml de mon portlet et >> ajouter esigate-core et esigate-servlet avec mes jar >> >> Bien cordialement >> -- >> Ahmed DRIRA >> Computer engineer >> S.A.R.L. Alpha Engineering - Tunisia >> Résidence El Habib, Bloc 3 - Bureaux 33 & 34 >> 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis >> | URL : www.alpha-engineering.net >> | Mob : 55 61 47 88 >> | Te : 71 96 49 06 >> | Fax : 71 96 41 53 >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Webassembletool-users mailing list >> Web...@li... >> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> > > > -- > Philippe De Oliveira > > -- Ahmed DRIRA Computer engineer S.A.R.L. Alpha Engineering - Tunisia Résidence El Habib, Bloc 3 - Bureaux 33 & 34 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis | URL : www.alpha-engineering.net | Mob : 55 61 47 88 | Te : 71 96 49 06 | Fax : 71 96 41 53 |
|
From: Philippe De O. <phi...@gm...> - 2014-10-23 09:19:27
|
Bonjour, Oui c'est possible, j'ai fais un PoC exactement comme ça il y a moins d'un an et ça fonctionne. Cordialement, 2014-10-22 22:00 GMT+02:00 Ahmed Drira <ahm...@gm...>: > Bonjour > est ce que possible de faire appel à esigate + esi:include pour intégrer > une application tiers dans ma portail à travers une portlet > bien sûre après avoir ajouter le filtre dans le web.xml de mon portlet et > ajouter esigate-core et esigate-servlet avec mes jar > > Bien cordialement > -- > Ahmed DRIRA > Computer engineer > S.A.R.L. Alpha Engineering - Tunisia > Résidence El Habib, Bloc 3 - Bureaux 33 & 34 > 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis > | URL : www.alpha-engineering.net > | Mob : 55 61 47 88 > | Te : 71 96 49 06 > | Fax : 71 96 41 53 > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > -- Philippe De Oliveira |
|
From: Ahmed D. <ahm...@gm...> - 2014-10-22 20:00:34
|
Bonjour est ce que possible de faire appel à esigate + esi:include pour intégrer une application tiers dans ma portail à travers une portlet bien sûre après avoir ajouter le filtre dans le web.xml de mon portlet et ajouter esigate-core et esigate-servlet avec mes jar Bien cordialement -- Ahmed DRIRA Computer engineer S.A.R.L. Alpha Engineering - Tunisia Résidence El Habib, Bloc 3 - Bureaux 33 & 34 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis | URL : www.alpha-engineering.net | Mob : 55 61 47 88 | Te : 71 96 49 06 | Fax : 71 96 41 53 |
|
From: Volker K. <vol...@gm...> - 2014-10-22 17:22:48
|
thanks for your very fast adjustments. I checked out the repository, but now I have problems wirth all submitted forms. They do not get the form data. I mean, the pages are not stateless, but as I am not caching the content in the moment, this should not be a problem. Up to know I did not had the time to debug it. I will do this some time later. 2014-10-20 15:59 GMT+02:00 Francois-Xavier Bonnet < fra...@ce...>: > Hi Volker, > > I have been able to reproduce and fix the 2 issues. Could you check with > the current head version that it works for you now? > > 2014-10-17 19:21 GMT+02:00 Francois-Xavier Bonnet < > fra...@ce...>: > >> I just entered the 2 issues on Github. >> https://github.com/esigate/esigate/issues/27 >> https://github.com/esigate/esigate/issues/28 >> >> 2014-10-16 9:08 GMT+02:00 Nicolas Richeton <nic...@gm...>: >> >>> Hi Volker, >>> >>> The proxy filter is a new addition to esigate 5.0. >>> Your feedback is really valuable to catch the last bugs before the >>> stable release, but if you want something that just work, you should try >>> esigate as a standalone proxy (esigate-server or esigate-war). >>> >>> We have several applications using esigate + wicket in production with >>> no issue. >>> >>> -- >>> Nicolas >>> >>> Le 15 oct. 2014 à 18:02, Volker Kümmer <vol...@gm...> a >>> écrit : >>> >>> hi >>> >>> good to know, that it should work in principle. >>> >>> I had not enough time, to really debug the problems, to see where it >>> originated from. >>> >>> But in the moment I am having two problems. >>> >>> 1. when the proxy filter is not in front of the wicket application, if I >>> send a redirect after a post, I get es 302 redirect. But when the ESIGate >>> proxy filter is in front of the application I will get an 307 redirect -- I >>> do not know why in the moment. >>> >>> 2. when using the wicket ajax mechanisms I will always get an error -- >>> it works without any problems without the proxy filter: >>> >>> java.lang.IllegalStateException: WRITER >>> at org.mortbay.jetty.Response.getOutputStream(Response.java:564) >>> at >>> org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) >>> at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) >>> at >>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) >>> at >>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) >>> at >>> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) >>> at >>> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) >>> at >>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) >>> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) >>> at >>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) >>> at org.mortbay.jetty.Server.handle(Server.java:295) >>> at >>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) >>> at >>> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) >>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) >>> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) >>> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) >>> at >>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) >>> at >>> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) >>> >>> >>> I am not using any esi or caching functionality. I have just configured >>> the proxyfilter before the application. I will see, if I can get some more >>> detailed information. >>> >>> >>> >>> 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet < >>> fra...@ce...>: >>> >>>> Hi Volker, >>>> >>>> The beta-1 versions is currently being tested on a few projects. Since >>>> this version, we have made a few improvements or bug fixes but no blocking >>>> issue. >>>> Usually we release a new beta version every time we find a blocking >>>> issue that need a fix and the stable release comes when a major project >>>> using EsiGate is ready to go to production. >>>> >>>> I would be very interested in having more information about the errors >>>> you have. If a beta-2 is required, we could release it very quickly. >>>> >>>> 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: >>>> >>>>> Hello >>>>> >>>>> I would like to know, what the current state of ESIGate is? >>>>> >>>>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get >>>>> ESIGate configured, so that it served some content. >>>>> >>>>> But now I get some errors. I have ESIGate in front of a wicket >>>>> application and there are some problems with it. So I would like to know, >>>>> whether there are some speciel configurations neccessary to get it working >>>>> or if the beta-1 from february 2014 is simply outdated, >>>>> >>>>> In the moment my application runs behind ESIGate, but I have not set >>>>> any caching headers up to now. So I expected that the application would >>>>> work as without ESIGate. >>>>> >>>>> If it should work with the beta-1 I will further investigate the >>>>> problem. But in the moment I just would like to know, if (these) problems >>>>> are to be expected, as it is still a beta. >>>>> >>>>> kind regards >>>>> Volker >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS >>>>> Reports >>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>>>> http://p.sf.net/sfu/Zoho >>>>> _______________________________________________ >>>>> Webassembletool-users mailing list >>>>> Web...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>>>> >>>>> >>>> >>> >>> ------------------------------------------------------------------------------ >>> Comprehensive Server Monitoring with Site24x7. >>> Monitor 10 servers for $9/Month. >>> Get alerted through email, SMS, voice calls or mobile push notifications. >>> Take corrective actions from your mobile device. >>> http://p.sf.net/sfu/Zoho >>> >>> _______________________________________________ >>> Webassembletool-users mailing list >>> Web...@li... >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Comprehensive Server Monitoring with Site24x7. >>> Monitor 10 servers for $9/Month. >>> Get alerted through email, SMS, voice calls or mobile push notifications. >>> Take corrective actions from your mobile device. >>> http://p.sf.net/sfu/Zoho >>> _______________________________________________ >>> Webassembletool-users mailing list >>> Web...@li... >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>> >>> >> > |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-10-20 16:03:34
|
Thank you very much for the code snippets. I created an issue for that in Github. I will try to see if I can integrate it. https://github.com/esigate/esigate/issues/33 2014-10-16 10:44 GMT+02:00 謝福明 <aug...@ch...>: > Hi, > > > > We have resolved this issue, > > > > Because InputStreamEntity writeTo() have to waiting buffer full > then write output, but our apps use long-polling transfers data never fill > up the buffer, cause InputStreamEntity waiting until timeout, > > > > So, > > 1. We add writeTo() in org.esigate.http.HttpResponseUtils, which > reference org.apache.http.entity.InputStreamEntity writeTo() method > > 2. insert outstream.flush() code after each outstream.write(buffer, > 0, l) method, > > 3. modify org.esigate.servlet.HttpServletMediator > httpEntity.writeTo(os) to > HttpResponseUtils.writeTo(httpEntity.getContentLength(), > httpEntity.getContent(), os); > > > > code snippets as below: > > *org.esigate.http.HttpResponseUtils * > > > > *public* *static* *void* writeTo(*long* length, InputStream content, > OutputStream outstream) *throws* IOException { > > *if* (outstream == *null*) { > > *throw* *new* IllegalArgumentException("Output stream may not > be null"); > > } > > > > InputStream instream = content; > > *try* { > > *byte*[] buffer = *new* *byte*[2048]; > > > > *if* (length < 0L) { > > *int* l; > > *while* ((l = instream.read(buffer)) != -1) { > > outstream.write(buffer, 0, l); > > outstream.flush(); > > } > > } > > > > *long* remaining = length; > > *while* (remaining > 0L) { > > *int* l = instream.read(buffer, 0, (*int*) Math.*min*(2048L, > remaining)); > > *if* (l == -1) { > > *break*; > > } > > outstream.write(buffer, 0, l); > > outstream.flush(); > > remaining -= l; > > } > > } *finally* { > > instream.close(); > > } > > > > } > > > > > > org.esigate.servlet.HttpServletMediator > > *public* *void* sendResponse(HttpResponse httpResponse) *throws* > IOException { > > . > > . > > . > > . > > *try* { > > ServletOutputStream os = response.getOutputStream(); > > // httpEntity.writeTo(*os*); > > HttpResponseUtils.*writeTo*(httpEntity.getContentLength(), > httpEntity.getContent(), os); > > } *catch* (IOException e) { > > *LOG*.warn("Error while sending the response", e); > > EntityUtils.*consume*(httpResponse.getEntity()); > > } > > } > > } > > > > > > > > > > > > *From:* fx....@gm... [mailto:fx....@gm...] *On Behalf Of *Francois-Xavier > Bonnet > *Sent:* Tuesday, September 30, 2014 1:00 AM > *To:* 謝福明 > *Cc:* Francois-Xavier Bonnet; web...@li... > > *Subject:* Re: [EsiGate-users] long-polling in esigate 4.1 problem > > > > Hi, > > > > How do you plan to use HttpAsyncClient? Are you going to migrate EsiGate > to HttpAsyncClient or write your own custom proxy servlet just for your > long polling requests? > > How can I help you? > > > > 2014-09-29 10:59 GMT+02:00 謝福明 <aug...@ch...>: > > > > Hi, > > > > “for a small response you may have to wait until the end of the > response to get the last packet”. Yes, we are encountering this problem… > > > > We decided to use HttpAsyncClient to resolve this problem, do you > have any suggestions? > > > > > > Thank you. > > *From:* fx....@gm... [mailto:fx....@gm...] *On Behalf Of *Francois-Xavier > Bonnet > *Sent:* Wednesday, September 24, 2014 9:54 PM > *To:* Francois-Xavier Bonnet > *Cc:* 謝福明; web...@li... > *Subject:* Re: [EsiGate-users] long-polling in esigate 4.1 problem > > > > I just had a look at the code. I can confirm that we are streaming > directly all non parsable responses but there might be a buffer issue: > currently it is flushed only when the buffer is full. So for a big > response, the response is streamed in packets which size depends on the > servlet container buffer size but for the last packet or for a small > response you may have to wait until the end of the response to get the last > packet. > > > > I guess this could explain the problem you have. > > > > Unfortunately this behavior cannot be changed easily because current > EsiGate version is based on Apache HttpClient, this implementation is using > blocking IO. I think we might be able to fix this after migrating to > HttpAsyncClient using event based content streaming like in this example > <https://hc.apache.org/httpcomponents-asyncclient-dev/httpasyncclient/examples/org/apache/http/examples/nio/client/AsyncClientHttpExchangeStreaming.java> but > this is planned for EsiGate 6.0 > > > > Feel free to open a bug report. Contributions are also always very much > appreciated. > > > > 2014-09-24 14:41 GMT+02:00 Francois-Xavier Bonnet < > fra...@ce...>: > > Hi Augustus, > > > > For content types like text/html and application/xhtml+xml, EsiGate is > buffering the complete response in order to parse it for ESI tags. You can > override this with "parsableContentTypes" property. > > For all other content-types, EsiGate is streaming directly the response to > the browser. > > What is the content-type header of the response you want to stream ? Which > application server are you using (there are some differences in the way > internal buffers work) ? What are the other response headers related to the > cache (Cache-control, Expires, Last-Modified, E-Tag) ? > > > > 2014-09-24 12:01 GMT+02:00 <aug...@ch...>: > > Hi, > > Dose esigate 4.1 can run in streaming mode?? It’s like fiddler > streaming mode > > > > > > We have problem when we use long-polling in esigate 4.1, > > > > user click execute button, long-polling will create channel > between client browser and backend Ap server through esigate， > > > > when channel is created, client browser will communicate with backend Ap > server, > > > > but it work always when esigate socketTimeout or websocket timeout, > > > > we found this problem in org.esigate.servlet.HttpServletMediator > line 193， > > > > when we click execute button, esigate will stop in > org.esigate.servlet.HttpServletMediator line 193 until it timeout, then work > > > > seems like esigate is waiting long-polling close, then it start do > response to client > > > > recently, we use fiddler access the app, it’s pending like > esigate, but when fiddler run in streaming mode, it’s works fine! > > > > So, esigate have streaming mode?? > > > > > > Thank you > > > > > > > > > > > *本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件. > 如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任. > Please be advised that this email message (including any attachments) > contains confidential information and may be legally privileged. If you are > not the intended recipient, please destroy this message and all attachments > from your system and do not further collect, process, or use them. Chunghwa > Telecom and all its subsidiaries and associated companies shall not be > liable for the improper or incomplete transmission of the information > contained in this email nor for any delay in its receipt or damage to your > system. If you are the intended recipient, please protect the confidential > and/or personal information contained in this email with due care. Any > unauthorized use, disclosure or distribution of this message in whole or in > part is strictly prohibited. Also, please self-inspect attachments and > hyperlinks contained in this email to ensure the information security and > to protect personal information.* > > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > > > > > > > ------------------------------------------------------------------------------ > Slashdot TV. Videos for Nerds. Stuff that Matters. > > http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-10-20 13:59:49
|
Hi Volker, I have been able to reproduce and fix the 2 issues. Could you check with the current head version that it works for you now? 2014-10-17 19:21 GMT+02:00 Francois-Xavier Bonnet < fra...@ce...>: > I just entered the 2 issues on Github. > https://github.com/esigate/esigate/issues/27 > https://github.com/esigate/esigate/issues/28 > > 2014-10-16 9:08 GMT+02:00 Nicolas Richeton <nic...@gm...>: > >> Hi Volker, >> >> The proxy filter is a new addition to esigate 5.0. >> Your feedback is really valuable to catch the last bugs before the stable >> release, but if you want something that just work, you should try esigate >> as a standalone proxy (esigate-server or esigate-war). >> >> We have several applications using esigate + wicket in production with no >> issue. >> >> -- >> Nicolas >> >> Le 15 oct. 2014 à 18:02, Volker Kümmer <vol...@gm...> a >> écrit : >> >> hi >> >> good to know, that it should work in principle. >> >> I had not enough time, to really debug the problems, to see where it >> originated from. >> >> But in the moment I am having two problems. >> >> 1. when the proxy filter is not in front of the wicket application, if I >> send a redirect after a post, I get es 302 redirect. But when the ESIGate >> proxy filter is in front of the application I will get an 307 redirect -- I >> do not know why in the moment. >> >> 2. when using the wicket ajax mechanisms I will always get an error -- it >> works without any problems without the proxy filter: >> >> java.lang.IllegalStateException: WRITER >> at org.mortbay.jetty.Response.getOutputStream(Response.java:564) >> at >> org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) >> at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) >> at >> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) >> at >> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) >> at >> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) >> at >> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) >> at >> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) >> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) >> at >> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) >> at org.mortbay.jetty.Server.handle(Server.java:295) >> at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) >> at >> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) >> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) >> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) >> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) >> at >> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) >> at >> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) >> >> >> I am not using any esi or caching functionality. I have just configured >> the proxyfilter before the application. I will see, if I can get some more >> detailed information. >> >> >> >> 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet < >> fra...@ce...>: >> >>> Hi Volker, >>> >>> The beta-1 versions is currently being tested on a few projects. Since >>> this version, we have made a few improvements or bug fixes but no blocking >>> issue. >>> Usually we release a new beta version every time we find a blocking >>> issue that need a fix and the stable release comes when a major project >>> using EsiGate is ready to go to production. >>> >>> I would be very interested in having more information about the errors >>> you have. If a beta-2 is required, we could release it very quickly. >>> >>> 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: >>> >>>> Hello >>>> >>>> I would like to know, what the current state of ESIGate is? >>>> >>>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get >>>> ESIGate configured, so that it served some content. >>>> >>>> But now I get some errors. I have ESIGate in front of a wicket >>>> application and there are some problems with it. So I would like to know, >>>> whether there are some speciel configurations neccessary to get it working >>>> or if the beta-1 from february 2014 is simply outdated, >>>> >>>> In the moment my application runs behind ESIGate, but I have not set >>>> any caching headers up to now. So I expected that the application would >>>> work as without ESIGate. >>>> >>>> If it should work with the beta-1 I will further investigate the >>>> problem. But in the moment I just would like to know, if (these) problems >>>> are to be expected, as it is still a beta. >>>> >>>> kind regards >>>> Volker >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>>> http://p.sf.net/sfu/Zoho >>>> _______________________________________________ >>>> Webassembletool-users mailing list >>>> Web...@li... >>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>>> >>>> >>> >> >> ------------------------------------------------------------------------------ >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> http://p.sf.net/sfu/Zoho >> >> _______________________________________________ >> Webassembletool-users mailing list >> Web...@li... >> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> >> >> ------------------------------------------------------------------------------ >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> http://p.sf.net/sfu/Zoho >> _______________________________________________ >> Webassembletool-users mailing list >> Web...@li... >> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> > |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-10-17 17:22:19
|
I just entered the 2 issues on Github. https://github.com/esigate/esigate/issues/27 https://github.com/esigate/esigate/issues/28 2014-10-16 9:08 GMT+02:00 Nicolas Richeton <nic...@gm...>: > Hi Volker, > > The proxy filter is a new addition to esigate 5.0. > Your feedback is really valuable to catch the last bugs before the stable > release, but if you want something that just work, you should try esigate > as a standalone proxy (esigate-server or esigate-war). > > We have several applications using esigate + wicket in production with no > issue. > > -- > Nicolas > > Le 15 oct. 2014 à 18:02, Volker Kümmer <vol...@gm...> a > écrit : > > hi > > good to know, that it should work in principle. > > I had not enough time, to really debug the problems, to see where it > originated from. > > But in the moment I am having two problems. > > 1. when the proxy filter is not in front of the wicket application, if I > send a redirect after a post, I get es 302 redirect. But when the ESIGate > proxy filter is in front of the application I will get an 307 redirect -- I > do not know why in the moment. > > 2. when using the wicket ajax mechanisms I will always get an error -- it > works without any problems without the proxy filter: > > java.lang.IllegalStateException: WRITER > at org.mortbay.jetty.Response.getOutputStream(Response.java:564) > at > org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) > at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) > at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) > at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) > at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) > at org.mortbay.jetty.Server.handle(Server.java:295) > at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) > at > org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) > at > org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) > > > I am not using any esi or caching functionality. I have just configured > the proxyfilter before the application. I will see, if I can get some more > detailed information. > > > > 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet < > fra...@ce...>: > >> Hi Volker, >> >> The beta-1 versions is currently being tested on a few projects. Since >> this version, we have made a few improvements or bug fixes but no blocking >> issue. >> Usually we release a new beta version every time we find a blocking issue >> that need a fix and the stable release comes when a major project using >> EsiGate is ready to go to production. >> >> I would be very interested in having more information about the errors >> you have. If a beta-2 is required, we could release it very quickly. >> >> 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: >> >>> Hello >>> >>> I would like to know, what the current state of ESIGate is? >>> >>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get >>> ESIGate configured, so that it served some content. >>> >>> But now I get some errors. I have ESIGate in front of a wicket >>> application and there are some problems with it. So I would like to know, >>> whether there are some speciel configurations neccessary to get it working >>> or if the beta-1 from february 2014 is simply outdated, >>> >>> In the moment my application runs behind ESIGate, but I have not set any >>> caching headers up to now. So I expected that the application would work as >>> without ESIGate. >>> >>> If it should work with the beta-1 I will further investigate the >>> problem. But in the moment I just would like to know, if (these) problems >>> are to be expected, as it is still a beta. >>> >>> kind regards >>> Volker >>> >>> >>> ------------------------------------------------------------------------------ >>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>> http://p.sf.net/sfu/Zoho >>> _______________________________________________ >>> Webassembletool-users mailing list >>> Web...@li... >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>> >>> >> > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-10-17 17:06:21
|
Bonjour, La documentation de la version 1.0 n'est plus en ligne mais l'ensemble du code source se trouve dans Github, y compris les sources de la documentation et le script ant qui permettait à l'époque de builder les jars et la doc. https://github.com/esigate/esigate/tree/1.0 Cela dit je pense que migrer à la dernière version serait une bonne idée. La version 1.0 date de 2008 et elle est basée sur Apache HttpClient 3 qui n'est plus supporté. Le https lui-même ne pose pas particulièrement de problème, ce sont plus les passages entre http et https selon les parties du site qui nécessitent un travail de mapping un peu plus complexe et parfois un peu de développement. Le 17 octobre 2014 17:01, Ludovic BERNARD <lud...@ap...> a écrit : > Bonjour à tous, > > > > Je travailles actuellement pour l’Apec sur la migration de la partie cms > ezpublish en HTTPS. > > > > Ils utilisent également une version 1.0 de WAT ( qui semble avoir été > customisé à l’époque pour leur besoins mais que l’apec n’a jamais modifié ). > > > > Les informations que j’ai actuellement sont que le WAT tourne dans tomcat. > > > > J’aimerais savoir s’il existe de la documentation sur cette version 1.0 et > la faisabilité de passer le système en https. > > > > Merci d’avance pour votre aide, > > Ludovic Bernard. > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
|
From: Ludovic B. <lud...@ap...> - 2014-10-17 15:21:25
|
Bonjour à tous, Je travailles actuellement pour l'Apec sur la migration de la partie cms ezpublish en HTTPS. Ils utilisent également une version 1.0 de WAT ( qui semble avoir été customisé à l'époque pour leur besoins mais que l'apec n'a jamais modifié ). Les informations que j'ai actuellement sont que le WAT tourne dans tomcat. J'aimerais savoir s'il existe de la documentation sur cette version 1.0 et la faisabilité de passer le système en https. Merci d'avance pour votre aide, Ludovic Bernard. |
|
From: 謝福明 <aug...@ch...> - 2014-10-16 08:45:36
|
Hi,
We have resolved this issue,
Because InputStreamEntity writeTo() have to waiting buffer full then write output, but our apps use long-polling transfers data never fill up the buffer, cause InputStreamEntity waiting until timeout,
So,
1. We add writeTo() in org.esigate.http.HttpResponseUtils, which reference org.apache.http.entity.InputStreamEntity writeTo() method
2. insert outstream.flush() code after each outstream.write(buffer, 0, l) method,
3. modify org.esigate.servlet.HttpServletMediator httpEntity.writeTo(os) to HttpResponseUtils.writeTo(httpEntity.getContentLength(), httpEntity.getContent(), os);
code snippets as below:
org.esigate.http.HttpResponseUtils
public static void writeTo(long length, InputStream content, OutputStream outstream) throws IOException {
if (outstream == null) {
throw new IllegalArgumentException("Output stream may not be null");
}
InputStream instream = content;
try {
byte[] buffer = new byte[2048];
if (length < 0L) {
int l;
while ((l = instream.read(buffer)) != -1) {
outstream.write(buffer, 0, l);
outstream.flush();
}
}
long remaining = length;
while (remaining > 0L) {
int l = instream.read(buffer, 0, (int) Math.min(2048L, remaining));
if (l == -1) {
break;
}
outstream.write(buffer, 0, l);
outstream.flush();
remaining -= l;
}
} finally {
instream.close();
}
}
org.esigate.servlet.HttpServletMediator
public void sendResponse(HttpResponse httpResponse) throws IOException {
.
.
.
.
try {
ServletOutputStream os = response.getOutputStream();
// httpEntity.writeTo(os);
HttpResponseUtils.writeTo(httpEntity.getContentLength(), httpEntity.getContent(), os);
} catch (IOException e) {
LOG.warn("Error while sending the response", e);
EntityUtils.consume(httpResponse.getEntity());
}
}
}
From: fx....@gm... [mailto:fx....@gm...] On Behalf Of Francois-Xavier Bonnet
Sent: Tuesday, September 30, 2014 1:00 AM
To: 謝福明
Cc: Francois-Xavier Bonnet; web...@li...
Subject: Re: [EsiGate-users] long-polling in esigate 4.1 problem
Hi,
How do you plan to use HttpAsyncClient? Are you going to migrate EsiGate to HttpAsyncClient or write your own custom proxy servlet just for your long polling requests?
How can I help you?
2014-09-29 10:59 GMT+02:00 謝福明 <aug...@ch...<mailto:aug...@ch...>>:
Hi,
“for a small response you may have to wait until the end of the response to get the last packet”. Yes, we are encountering this problem…
We decided to use HttpAsyncClient to resolve this problem, do you have any suggestions?
Thank you.
From: fx....@gm...<mailto:fx....@gm...> [mailto:fx....@gm...<mailto:fx....@gm...>] On Behalf Of Francois-Xavier Bonnet
Sent: Wednesday, September 24, 2014 9:54 PM
To: Francois-Xavier Bonnet
Cc: 謝福明; web...@li...<mailto:web...@li...>
Subject: Re: [EsiGate-users] long-polling in esigate 4.1 problem
I just had a look at the code. I can confirm that we are streaming directly all non parsable responses but there might be a buffer issue: currently it is flushed only when the buffer is full. So for a big response, the response is streamed in packets which size depends on the servlet container buffer size but for the last packet or for a small response you may have to wait until the end of the response to get the last packet.
I guess this could explain the problem you have.
Unfortunately this behavior cannot be changed easily because current EsiGate version is based on Apache HttpClient, this implementation is using blocking IO. I think we might be able to fix this after migrating to HttpAsyncClient using event based content streaming like in this example<https://hc.apache.org/httpcomponents-asyncclient-dev/httpasyncclient/examples/org/apache/http/examples/nio/client/AsyncClientHttpExchangeStreaming.java> but this is planned for EsiGate 6.0
Feel free to open a bug report. Contributions are also always very much appreciated.
2014-09-24 14:41 GMT+02:00 Francois-Xavier Bonnet <fra...@ce...<mailto:fra...@ce...>>:
Hi Augustus,
For content types like text/html and application/xhtml+xml, EsiGate is buffering the complete response in order to parse it for ESI tags. You can override this with "parsableContentTypes" property.
For all other content-types, EsiGate is streaming directly the response to the browser.
What is the content-type header of the response you want to stream ? Which application server are you using (there are some differences in the way internal buffers work) ? What are the other response headers related to the cache (Cache-control, Expires, Last-Modified, E-Tag) ?
2014-09-24 12:01 GMT+02:00 <aug...@ch...<mailto:aug...@ch...>>:
Hi,
Dose esigate 4.1 can run in streaming mode?? It’s like fiddler streaming mode
We have problem when we use long-polling in esigate 4.1,
user click execute button, long-polling will create channel between client browser and backend Ap server through esigate，
when channel is created, client browser will communicate with backend Ap server,
but it work always when esigate socketTimeout or websocket timeout,
we found this problem in org.esigate.servlet.HttpServletMediator line 193，
when we click execute button, esigate will stop in org.esigate.servlet.HttpServletMediator line 193 until it timeout, then work
seems like esigate is waiting long-polling close, then it start do response to client
recently, we use fiddler access the app, it’s pending like esigate, but when fiddler run in streaming mode, it’s works fine!
So, esigate have streaming mode??
Thank you
本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件. 如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任.
Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Webassembletool-users mailing list
Web...@li...<mailto:Web...@li...>
https://lists.sourceforge.net/lists/listinfo/webassembletool-users
------------------------------------------------------------------------------
Slashdot TV. Videos for Nerds. Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
Webassembletool-users mailing list
Web...@li...<mailto:Web...@li...>
https://lists.sourceforge.net/lists/listinfo/webassembletool-users
|
|
From: Nicolas R. <nic...@gm...> - 2014-10-16 07:09:01
|
Hi Volker, The proxy filter is a new addition to esigate 5.0. Your feedback is really valuable to catch the last bugs before the stable release, but if you want something that just work, you should try esigate as a standalone proxy (esigate-server or esigate-war). We have several applications using esigate + wicket in production with no issue. -- Nicolas > Le 15 oct. 2014 à 18:02, Volker Kümmer <vol...@gm...> a écrit : > > hi > > good to know, that it should work in principle. > > I had not enough time, to really debug the problems, to see where it originated from. > > But in the moment I am having two problems. > > 1. when the proxy filter is not in front of the wicket application, if I send a redirect after a post, I get es 302 redirect. But when the ESIGate proxy filter is in front of the application I will get an 307 redirect -- I do not know why in the moment. > > 2. when using the wicket ajax mechanisms I will always get an error -- it works without any problems without the proxy filter: > > java.lang.IllegalStateException: WRITER > at org.mortbay.jetty.Response.getOutputStream(Response.java:564) > at org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) > at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) > at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) > at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) > at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) > at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) > at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) > at org.mortbay.jetty.Server.handle(Server.java:295) > at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) > at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) > at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) > at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) > > > I am not using any esi or caching functionality. I have just configured the proxyfilter before the application. I will see, if I can get some more detailed information. > > > > 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet <fra...@ce...>: >> Hi Volker, >> >> The beta-1 versions is currently being tested on a few projects. Since this version, we have made a few improvements or bug fixes but no blocking issue. >> Usually we release a new beta version every time we find a blocking issue that need a fix and the stable release comes when a major project using EsiGate is ready to go to production. >> >> I would be very interested in having more information about the errors you have. If a beta-2 is required, we could release it very quickly. >> >> 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: >>> Hello >>> >>> I would like to know, what the current state of ESIGate is? >>> >>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get ESIGate configured, so that it served some content. >>> >>> But now I get some errors. I have ESIGate in front of a wicket application and there are some problems with it. So I would like to know, whether there are some speciel configurations neccessary to get it working or if the beta-1 from february 2014 is simply outdated, >>> >>> In the moment my application runs behind ESIGate, but I have not set any caching headers up to now. So I expected that the application would work as without ESIGate. >>> >>> If it should work with the beta-1 I will further investigate the problem. But in the moment I just would like to know, if (these) problems are to be expected, as it is still a beta. >>> >>> kind regards >>> Volker >>> >>> ------------------------------------------------------------------------------ >>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>> http://p.sf.net/sfu/Zoho >>> _______________________________________________ >>> Webassembletool-users mailing list >>> Web...@li... >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-10-15 20:38:18
|
Good catch. 1) is a bug: org/esigate/servlet/impl/ResponseCapturingWrapper is using HttpStatus.SC_TEMPORARY_REDIRECT instead of HttpStatus.SC_MOVED_TEMPORARILY http://www.esigate.org/5.0-beta-2/esigate-servlet/xref/org/esigate/servlet/impl/ResponseCapturingWrapper.html#L126 2) is probably also a bug but needs more investigation to be reproduced. When the ResponseSender is used, the response should not be committed yet. 2014-10-15 22:08 GMT+02:00 Volker Kümmer <vol...@gm...>: > wicket is using for the AjaxResponse a writer and not an outputstream. > That means, a writer was already opened. So when ESIGate ist calling > > httpEntity.writeTo(response.getOutputStream()); // in ResponseSender > > it will get an exception, because an output stream could not be created, > as there was already a writer created for the response -> > IllegalArgumentException > > > > 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet < > fra...@ce...>: > >> Hi Volker, >> >> The beta-1 versions is currently being tested on a few projects. Since >> this version, we have made a few improvements or bug fixes but no blocking >> issue. >> Usually we release a new beta version every time we find a blocking issue >> that need a fix and the stable release comes when a major project using >> EsiGate is ready to go to production. >> >> I would be very interested in having more information about the errors >> you have. If a beta-2 is required, we could release it very quickly. >> >> 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: >> >>> Hello >>> >>> I would like to know, what the current state of ESIGate is? >>> >>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get >>> ESIGate configured, so that it served some content. >>> >>> But now I get some errors. I have ESIGate in front of a wicket >>> application and there are some problems with it. So I would like to know, >>> whether there are some speciel configurations neccessary to get it working >>> or if the beta-1 from february 2014 is simply outdated, >>> >>> In the moment my application runs behind ESIGate, but I have not set any >>> caching headers up to now. So I expected that the application would work as >>> without ESIGate. >>> >>> If it should work with the beta-1 I will further investigate the >>> problem. But in the moment I just would like to know, if (these) problems >>> are to be expected, as it is still a beta. >>> >>> kind regards >>> Volker >>> >>> >>> ------------------------------------------------------------------------------ >>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>> http://p.sf.net/sfu/Zoho >>> _______________________________________________ >>> Webassembletool-users mailing list >>> Web...@li... >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>> >>> >> > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
|
From: Volker K. <vol...@gm...> - 2014-10-15 20:08:43
|
wicket is using for the AjaxResponse a writer and not an outputstream. That means, a writer was already opened. So when ESIGate ist calling httpEntity.writeTo(response.getOutputStream()); // in ResponseSender it will get an exception, because an output stream could not be created, as there was already a writer created for the response -> IllegalArgumentException 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet < fra...@ce...>: > Hi Volker, > > The beta-1 versions is currently being tested on a few projects. Since > this version, we have made a few improvements or bug fixes but no blocking > issue. > Usually we release a new beta version every time we find a blocking issue > that need a fix and the stable release comes when a major project using > EsiGate is ready to go to production. > > I would be very interested in having more information about the errors you > have. If a beta-2 is required, we could release it very quickly. > > 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: > >> Hello >> >> I would like to know, what the current state of ESIGate is? >> >> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get >> ESIGate configured, so that it served some content. >> >> But now I get some errors. I have ESIGate in front of a wicket >> application and there are some problems with it. So I would like to know, >> whether there are some speciel configurations neccessary to get it working >> or if the beta-1 from february 2014 is simply outdated, >> >> In the moment my application runs behind ESIGate, but I have not set any >> caching headers up to now. So I expected that the application would work as >> without ESIGate. >> >> If it should work with the beta-1 I will further investigate the problem. >> But in the moment I just would like to know, if (these) problems are to be >> expected, as it is still a beta. >> >> kind regards >> Volker >> >> >> ------------------------------------------------------------------------------ >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >> http://p.sf.net/sfu/Zoho >> _______________________________________________ >> Webassembletool-users mailing list >> Web...@li... >> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> > |
|
From: Volker K. <vol...@gm...> - 2014-10-15 16:02:34
|
hi good to know, that it should work in principle. I had not enough time, to really debug the problems, to see where it originated from. But in the moment I am having two problems. 1. when the proxy filter is not in front of the wicket application, if I send a redirect after a post, I get es 302 redirect. But when the ESIGate proxy filter is in front of the application I will get an 307 redirect -- I do not know why in the moment. 2. when using the wicket ajax mechanisms I will always get an error -- it works without any problems without the proxy filter: java.lang.IllegalStateException: WRITER at org.mortbay.jetty.Response.getOutputStream(Response.java:564) at org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:295) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) I am not using any esi or caching functionality. I have just configured the proxyfilter before the application. I will see, if I can get some more detailed information. 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet < fra...@ce...>: > Hi Volker, > > The beta-1 versions is currently being tested on a few projects. Since > this version, we have made a few improvements or bug fixes but no blocking > issue. > Usually we release a new beta version every time we find a blocking issue > that need a fix and the stable release comes when a major project using > EsiGate is ready to go to production. > > I would be very interested in having more information about the errors you > have. If a beta-2 is required, we could release it very quickly. > > 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: > >> Hello >> >> I would like to know, what the current state of ESIGate is? >> >> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get >> ESIGate configured, so that it served some content. >> >> But now I get some errors. I have ESIGate in front of a wicket >> application and there are some problems with it. So I would like to know, >> whether there are some speciel configurations neccessary to get it working >> or if the beta-1 from february 2014 is simply outdated, >> >> In the moment my application runs behind ESIGate, but I have not set any >> caching headers up to now. So I expected that the application would work as >> without ESIGate. >> >> If it should work with the beta-1 I will further investigate the problem. >> But in the moment I just would like to know, if (these) problems are to be >> expected, as it is still a beta. >> >> kind regards >> Volker >> >> >> ------------------------------------------------------------------------------ >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >> http://p.sf.net/sfu/Zoho >> _______________________________________________ >> Webassembletool-users mailing list >> Web...@li... >> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> > |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-10-15 07:25:04
|
Hi Volker, The beta-1 versions is currently being tested on a few projects. Since this version, we have made a few improvements or bug fixes but no blocking issue. Usually we release a new beta version every time we find a blocking issue that need a fix and the stable release comes when a major project using EsiGate is ready to go to production. I would be very interested in having more information about the errors you have. If a beta-2 is required, we could release it very quickly. 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: > Hello > > I would like to know, what the current state of ESIGate is? > > I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get > ESIGate configured, so that it served some content. > > But now I get some errors. I have ESIGate in front of a wicket application > and there are some problems with it. So I would like to know, whether there > are some speciel configurations neccessary to get it working or if the > beta-1 from february 2014 is simply outdated, > > In the moment my application runs behind ESIGate, but I have not set any > caching headers up to now. So I expected that the application would work as > without ESIGate. > > If it should work with the beta-1 I will further investigate the problem. > But in the moment I just would like to know, if (these) problems are to be > expected, as it is still a beta. > > kind regards > Volker > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://p.sf.net/sfu/Zoho > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
|
From: Volker K. <vol...@gm...> - 2014-10-13 15:35:26
|
Hello I would like to know, what the current state of ESIGate is? I was able (with the help of Francois-Xavier Bonnet -- thanks!) to get ESIGate configured, so that it served some content. But now I get some errors. I have ESIGate in front of a wicket application and there are some problems with it. So I would like to know, whether there are some speciel configurations neccessary to get it working or if the beta-1 from february 2014 is simply outdated, In the moment my application runs behind ESIGate, but I have not set any caching headers up to now. So I expected that the application would work as without ESIGate. If it should work with the beta-1 I will further investigate the problem. But in the moment I just would like to know, if (these) problems are to be expected, as it is still a beta. kind regards Volker |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-10-08 16:26:57
|
Hello Volker, Yes the servlet filter can be used in front of an application and will use its cache but depending on the configuration and on the headers set in the responses of the application. Could you send your esigate.properties configuration file? 2014-10-08 18:07 GMT+02:00 Volker Kümmer <vol...@gm...>: > Hello > > I tried to configure the esigate filter, but I was not successfull. > Probably I did not understand it correctly. > > So my question is: > > is it possible, to use the servlet filter (as filter in java are normally > used) in front of an applocation. Configuring it in a way, that the esi > gate filter is the first one in the chain. It should therefore just let a > request through to the application and cache the content according the the > headers set from the application. > > I do not want to assemble content from different sites, just from the java > application, that comes after the esigate filter in the filter chain. In > the documetation I have not found an example for this kind of > configuration. Just examples, where esigate is an application for itself, > that delegates the requests to different backends. > > I tried to configure it for this configuration, but was not successfull. I > always got a timeout error. > > kind regards > volker > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
|
From: Volker K. <vol...@gm...> - 2014-10-08 16:08:03
|
Hello I tried to configure the esigate filter, but I was not successfull. Probably I did not understand it correctly. So my question is: is it possible, to use the servlet filter (as filter in java are normally used) in front of an applocation. Configuring it in a way, that the esi gate filter is the first one in the chain. It should therefore just let a request through to the application and cache the content according the the headers set from the application. I do not want to assemble content from different sites, just from the java application, that comes after the esigate filter in the filter chain. In the documetation I have not found an example for this kind of configuration. Just examples, where esigate is an application for itself, that delegates the requests to different backends. I tried to configure it for this configuration, but was not successfull. I always got a timeout error. kind regards volker |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-09-29 17:00:39
|
Hi, How do you plan to use HttpAsyncClient? Are you going to migrate EsiGate to HttpAsyncClient or write your own custom proxy servlet just for your long polling requests? How can I help you? 2014-09-29 10:59 GMT+02:00 謝福明 <aug...@ch...>: > > > Hi, > > > > “for a small response you may have to wait until the end of the > response to get the last packet”. Yes, we are encountering this problem… > > > > We decided to use HttpAsyncClient to resolve this problem, do you > have any suggestions? > > > > > > Thank you. > > *From:* fx....@gm... [mailto:fx....@gm...] *On Behalf Of *Francois-Xavier > Bonnet > *Sent:* Wednesday, September 24, 2014 9:54 PM > *To:* Francois-Xavier Bonnet > *Cc:* 謝福明; web...@li... > *Subject:* Re: [EsiGate-users] long-polling in esigate 4.1 problem > > > > I just had a look at the code. I can confirm that we are streaming > directly all non parsable responses but there might be a buffer issue: > currently it is flushed only when the buffer is full. So for a big > response, the response is streamed in packets which size depends on the > servlet container buffer size but for the last packet or for a small > response you may have to wait until the end of the response to get the last > packet. > > > > I guess this could explain the problem you have. > > > > Unfortunately this behavior cannot be changed easily because current > EsiGate version is based on Apache HttpClient, this implementation is using > blocking IO. I think we might be able to fix this after migrating to > HttpAsyncClient using event based content streaming like in this example > <https://hc.apache.org/httpcomponents-asyncclient-dev/httpasyncclient/examples/org/apache/http/examples/nio/client/AsyncClientHttpExchangeStreaming.java> but > this is planned for EsiGate 6.0 > > > > Feel free to open a bug report. Contributions are also always very much > appreciated. > > > > 2014-09-24 14:41 GMT+02:00 Francois-Xavier Bonnet < > fra...@ce...>: > > Hi Augustus, > > > > For content types like text/html and application/xhtml+xml, EsiGate is > buffering the complete response in order to parse it for ESI tags. You can > override this with "parsableContentTypes" property. > > For all other content-types, EsiGate is streaming directly the response to > the browser. > > What is the content-type header of the response you want to stream ? Which > application server are you using (there are some differences in the way > internal buffers work) ? What are the other response headers related to the > cache (Cache-control, Expires, Last-Modified, E-Tag) ? > > > > 2014-09-24 12:01 GMT+02:00 <aug...@ch...>: > > Hi, > > Dose esigate 4.1 can run in streaming mode?? It’s like fiddler > streaming mode > > > > > > We have problem when we use long-polling in esigate 4.1, > > > > user click execute button, long-polling will create channel > between client browser and backend Ap server through esigate， > > > > when channel is created, client browser will communicate with backend Ap > server, > > > > but it work always when esigate socketTimeout or websocket timeout, > > > > we found this problem in org.esigate.servlet.HttpServletMediator > line 193， > > > > when we click execute button, esigate will stop in > org.esigate.servlet.HttpServletMediator line 193 until it timeout, then work > > > > seems like esigate is waiting long-polling close, then it start do > response to client > > > > recently, we use fiddler access the app, it’s pending like > esigate, but when fiddler run in streaming mode, it’s works fine! > > > > So, esigate have streaming mode?? > > > > > > Thank you > > > > > > > > > > > *本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件. > 如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任. > Please be advised that this email message (including any attachments) > contains confidential information and may be legally privileged. If you are > not the intended recipient, please destroy this message and all attachments > from your system and do not further collect, process, or use them. Chunghwa > Telecom and all its subsidiaries and associated companies shall not be > liable for the improper or incomplete transmission of the information > contained in this email nor for any delay in its receipt or damage to your > system. If you are the intended recipient, please protect the confidential > and/or personal information contained in this email with due care. Any > unauthorized use, disclosure or distribution of this message in whole or in > part is strictly prohibited. Also, please self-inspect attachments and > hyperlinks contained in this email to ensure the information security and > to protect personal information.* > > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > > > > > > ------------------------------------------------------------------------------ > Slashdot TV. Videos for Nerds. Stuff that Matters. > > http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
5 messages has been excluded from this view by a project administrator.
