Mark, Looks like tar/zip attachments are getting removed.
Uploaded same in google drive now. Please let me know if you can access the same or not. https://drive.google.com/open?id=0B1OzquDqWi6bVUN0MDk2RDFENG8 Thanks, Durga Srinivasu On Mon, Dec 19, 2016 at 3:21 PM, Durga Srinivasu Karuturi < durgasriniv...@gmail.com> wrote: > Mark, > > Attaching the modified ROOT web-app from tomcat 8.5.9 bundle. Just changed > index.jsp and added lib [mostly DOJO] folder content to reproduce. > > If we deploy this in latest 8.5.9 with http2 enabled in chrome we are > seeing the SPDY compression errors > > Please let me know if this helps. > > Thanks, > Durga Srinivasu > > > > On Mon, Dec 19, 2016 at 2:31 PM, Mark Thomas <ma...@apache.org> wrote: > >> On 17/12/2016 06:35, Durga Srinivasu Karuturi wrote: >> > Do i need to post in any other forum? >> >> No, you are in the right place. >> >> You mentioned the issue was reproducible with the Dojo libraries. If you >> can provide the simplest possible set of steps to recreate this issue >> from a clean Tomcat 8.5.9 install that would be a big help. >> >> Mark >> >> > >> > Thanks, >> > Durga Srinivasu >> > >> > On Thu, Dec 15, 2016 at 6:41 PM, Durga Srinivasu Karuturi >> > <durgasriniv...@gmail.com <mailto:durgasriniv...@gmail.com>> wrote: >> > >> > Hi, >> > >> > Any pointers please? >> > >> > Thanks, >> > Durga Srinivasu >> > >> > On Wed, Dec 14, 2016 at 10:15 PM, Durga Srinivasu Karuturi >> > <durgasriniv...@gmail.com <mailto:durgasriniv...@gmail.com>> wrote: >> > >> > Hi, >> > >> > Recent chrome [Mac - Sierra : Version 55.0.2883.87 (64-bit) ] >> we are seeing issues in http2 sites. >> > >> > >> > Initially we have seen problem with http2 table header size >> limit error and to fix this, we have upgraded tomcat 8.5.4 to 8.5.9 where >> tomcat has increased the header limit from 16K to 64K. >> > >> > >> > Now with latest tomcat 8.5.9 we are seeing >> ERR_SPDY_COMPRESSION_ERROR while loading dojo libraries. >> > >> > Tried couple of steps (flush SPDY sokets etc) based on google >> search on this issue but nothing worked.. >> > >> > >> > Inline image 1 >> > >> > t=10513 [st= 1] -HTTP_TRANSACTION_SEND_REQUEST >> > >> > t=10513 [st= 1] +HTTP_TRANSACTION_READ_HEADERS [dt=36] >> > >> > t=10549 [st=37] HTTP2_STREAM_ERROR >> > >> > --> description = "ABANDONED >> > (stream_id=139): >> > https://10.104.118.174/webacs/lib/dijit/form/_ToggleB >> uttonMixin.js.map >> > <https://10.104.118.174/webacs/lib/dijit/form/_ToggleButton >> Mixin.js.map>" >> > >> > --> status = -363 >> > >> > --> stream_id = 139 >> > >> > t=10549 [st=37] -HTTP_TRANSACTION_READ_HEADERS >> > >> > * --> net_error = -363 >> > (ERR_SPDY_COMPRESSION_ERROR)* >> > >> > t=10549 [st=37] -URL_REQUEST_START_JOB >> > >> > * --> net_error = -363 >> > (ERR_SPDY_COMPRESSION_ERROR)* >> > >> > t=10549 [st=37] URL_REQUEST_DELEGATE [dt=0] >> > >> > t=10549 [st=37] -REQUEST_ALIVE >> > >> > --> net_error = -363 >> (ERR_SPDY_COMPRESSION_ERROR) >> > >> > >> > Initial content is downloaded (other JS files etc) but on some >> dojo libraries alone, we are this issue which make application home page >> load fails. >> > >> > >> > Firefox works! >> > >> > >> > We are having latest tomcat 8.5.9 already. Not sure where else >> problem now. We have not enabled any compression server side. >> > >> > >> > https://bugs.chromium.org/p/chromium/issues/detail?id=673315 >> > <https://bugs.chromium.org/p/chromium/issues/detail?id=673315> >> (Chrome bugs i have raised) >> > >> > My guess is that the bug is in Tomcat, in that it does not >> send an HPACK dynamic table size update (so the dynamic table should be the >> default 4 kB) but uses a 64 kB dynamic table. >> > As soon as it references entries that are in fact already >> emitted, that's a compression error. >> > See https://www.ietf.org/mail-arch >> ive/web/httpbisa/current/msg27867.html >> > <https://www.ietf.org/mail-archive/web/httpbisa/current/msg >> 27867.html> for a discussion on how to interpret the specs. >> > >> > According to the chrome bug notes problem is with tome dynamic >> table size 64k. I don't know how to confirm this is as tomcat issue as well. >> > >> > Can somebody help here to trace the problem? >> > >> > >> > >> > >> > >> > >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >
