From: Nicolas R. <nic...@gm...> - 2014-04-23 17:09:56
|
Hi Johann, We never hit this issue. Esigate is in production on very large pages. Feel free to open a bug to discuss on it. We will need more details : - Which esigate version are you using ? - What is your setup esigate-server (standalone) / esigate-war (WAR in tomcat/other) / esigate-core (API) - logs (fetch.log/fragment.log) - configuration esigate.properties - backend/provider server used - does your backend/provider application uses any of these : 100-continue, long-polling, websockets ? Nicolas Le 23 avr. 2014 à 17:55, Johann Böhler <joh...@1u...> a écrit : > Hi guys, > > I just had a look at your library and it’s really pretty awesome. > > But I have problem when I’m starting to render pages which exceed 2KB in size. First I got the error message > > Received incomplete response with Content-Length 12341234 but actual body length 2048 > > @ BasicHttpCache in http-client > > When I turned off caching, the website to display gets cut after it hits the 2KB limit. So basically I can only see the header of the website. > Can you help me? > > Best regards, > Johann > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform_______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users |