Re: [Resin-interest] Binary image prepending http response
Hi Serge, Thanks for your reply. The binary data is not random. Rather it is other resources, such as images, which included (eg with tags) in the page. For some reason these resources are being prepended to the page. We do use filters. Thanks for the suggestion. We will look into this lead. Thanks, SaM On 7/12/07, Serge Knystautas <[EMAIL PROTECTED]> wrote: > Samuel, > > Resin isn't really smart enough to make up random binary content, so I > would try to identify what that binary content and then hope to locate a > source of it (a file, a servlet, whatever). > > Are you using filters by any chance? This is a leap, but it seems like > this is a servlet spec interpretation/implementation difference (or an > implementation of something not clear in the spec). The most common > thing I've seen with Resin and Tomcat is how filters are handled. > > But I would try to identify what that binary content is... maybe it's an > ad from a hacked program for all we know... but I think identifying that > will give clues as to what could be inserting it. > > -- > Serge Knystautas > Lokitech >> software . strategy . design >> http://www.lokitech.com > p. 301.656.5501 > e. [EMAIL PROTECTED] > > Samuel Le Berrigaud wrote: > > Hi all, > > > > Here is the problem we're facing: > > > > - Do a simple GET request to the server, the page we request is a > > 'normal' html page containing images, js, css, etc... > > - From time to time the response to the HTTP request comes back as > > binary data where we expect a document for which the content type is > > text/html. > > > > We tried the same webapp with the exact same configuration on a Tomcat > > server and couldn't reproduce the problem. We haven't seen it on the > > many other application servers our application runs on either. > > However several customers reported the issue when using Resin 3.0.x. > > We therefore assume the issue comes from Resin. We tested a range of > > Resin versions from 3.0.15 to 3.0.23. > > > > Attached is an example of a file we get back as binary content. It > > indeed contains binary data as well as the expected html… > > > > Another thing is that we have the 'keep-alive' attribute set on our > > requests and first wondered if it could have been the problem. Turning > > it off didn't solve the problem though. > > > > Any help would be appreciated. We understand that the information on > > this issue is a bit sparse but we couldn't think of anything else. > > Looking at the HTTP headers didn't help. Hopefully someone will have > > encountered this before and will be able to advise us on what is going > > on. > > > > Thanks, > > > > ___ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest > -- Samuel Le Berrigaud ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Binary image prepending http response
Samuel, Resin isn't really smart enough to make up random binary content, so I would try to identify what that binary content and then hope to locate a source of it (a file, a servlet, whatever). Are you using filters by any chance? This is a leap, but it seems like this is a servlet spec interpretation/implementation difference (or an implementation of something not clear in the spec). The most common thing I've seen with Resin and Tomcat is how filters are handled. But I would try to identify what that binary content is... maybe it's an ad from a hacked program for all we know... but I think identifying that will give clues as to what could be inserting it. -- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED] Samuel Le Berrigaud wrote: > Hi all, > > Here is the problem we're facing: > > - Do a simple GET request to the server, the page we request is a > 'normal' html page containing images, js, css, etc... > - From time to time the response to the HTTP request comes back as > binary data where we expect a document for which the content type is > text/html. > > We tried the same webapp with the exact same configuration on a Tomcat > server and couldn't reproduce the problem. We haven't seen it on the > many other application servers our application runs on either. > However several customers reported the issue when using Resin 3.0.x. > We therefore assume the issue comes from Resin. We tested a range of > Resin versions from 3.0.15 to 3.0.23. > > Attached is an example of a file we get back as binary content. It > indeed contains binary data as well as the expected html… > > Another thing is that we have the 'keep-alive' attribute set on our > requests and first wondered if it could have been the problem. Turning > it off didn't solve the problem though. > > Any help would be appreciated. We understand that the information on > this issue is a bit sparse but we couldn't think of anything else. > Looking at the HTTP headers didn't help. Hopefully someone will have > encountered this before and will be able to advise us on what is going > on. > > Thanks, ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Binary image prepending http response
As always I forgot the attachment. SaM On 7/12/07, Samuel Le Berrigaud <[EMAIL PROTECTED]> wrote: Hi all, Here is the problem we're facing: - Do a simple GET request to the server, the page we request is a 'normal' html page containing images, js, css, etc... - From time to time the response to the HTTP request comes back as binary data where we expect a document for which the content type is text/html. We tried the same webapp with the exact same configuration on a Tomcat server and couldn't reproduce the problem. We haven't seen it on the many other application servers our application runs on either. However several customers reported the issue when using Resin 3.0.x. We therefore assume the issue comes from Resin. We tested a range of Resin versions from 3.0.15 to 3.0.23. Attached is an example of a file we get back as binary content. It indeed contains binary data as well as the expected html… Another thing is that we have the 'keep-alive' attribute set on our requests and first wondered if it could have been the problem. Turning it off didn't solve the problem though. Any help would be appreciated. We understand that the information on this issue is a bit sparse but we couldn't think of anything else. Looking at the HTTP headers didn't help. Hopefully someone will have encountered this before and will be able to advise us on what is going on. Thanks, -- Samuel Le Berrigaud -- Samuel Le Berrigaud 5R/ÐÀd00yhÉm.0Cð\7ÁL¥©±(Ðð¬q|¤Hõ`9¯¶c2Àzà; ©gnC2õ)÷IRúÉÜæÜ 5 j x ¶¡ ¯¡à Ü©ê?8º8²)öVX×t2¸ßAïydÕ'D.Ir3[EMAIL PROTECTED]@¦H c?¤²Sÿ¡ÿDXG1Dþ\p=õhZTtI`9g?¨ðå ®À|Pê #Çdó¦6 ¦lØ p°Q§wyÚP{'᧽ ¨ ÷HèÖ j¨z¦¨zª:[EMAIL PROTECTED]@èu=ïtGv=FðsïYnKç¡`+¤¯¸\êÉ|[EMAIL PROTECTED](p ø ®tû6էتÜ|p®âä:¢æ誮#Ê®Hà®ð¯Â0¯¯P¯÷êþùº¯7ЯÿZ;°&P°[ »° »ü1|ÇÕ*¤)ð¶£Q<ódß®ös×ÓfMybp34)Gpm×MÁ+§p ݱ¦` P ÜÆl ÿÈdg 0 L¶ ÿøj L+Ñè~÷pqrñ ´§zb´HËJ;LK"µ7 [EMAIL PROTECTED] f¶jëlÛnK[EMAIL PROTECTED] [¸1ÿ1Ið+1\`Ë°E>ùç [EMAIL PROTECTED] ¶ ~êLÌhþÈ¥¶L¦¦C ¦6 »V¥ ®(vm'7Ïf¡ZÁÄ!YS±Â°L3Vÿ$]Ê Õ&O4çLi{= Djv7Á\â¾É góf©÷°[+Äuï;oiË ¦¦jjMÐÿȦ>)övÑmÿÔO» ~^gÀèÀW' |±Á)\ÁpÁ|Ì!7$&ÂE Â,ì .|¦EÃ3LÃ6é»ÃðÐÃ?,AÌOC¼ EwµÁpÀþ_áÀ÷{ª³À[EMAIL PROTECTED]ec8pµgû¿/çB O»[x°è7o%ààêL,ðÈZ£Ëº[pòOÐ [EMAIL PROTECTED] Èô÷+¼§=TU°¬É0ÉìPÉVpÉyÉlÊ+,£| ¥\§l©«¼ \ ¯,[EMAIL PROTECTED](>ò+cKÈWÌ=åÌTkõÈà FjªZà[tQU iëLÎÄ j¶ää]ÅmëÌ°¼®µ ]ÃéÀþ(cG½ F,QÏ÷#ù<û|È#TWн }Ð8Ð- ýÐ-Ñí - m ½ Í "½$]&}Ò)½ÒsØÒQöÒ1ݹÑq 7(M(rp%(V 9oÜÔ«¦¹l ªqèµjfo_ð%ðÈêEDPýxÎÔýóætŦ\]yÛÙÔ@ mèg -¦çpë°B÷Ð)l¹ÖáÖ2P9-×ýB׸kw×E°×}]Øó0Ø }Ø°ØýØ=Ù Y ½ þÝÜ·Úâ0Ú¥½§}ªÍÚ¥xÌ4ñ48Ml6x©sülw¡l½°Bj¦fÉXj~á º}û§TÐÌg©uë=¸0 CÞÀ|&=êõÕÿH Ù ð0]ÌdñRÅà·Ù-ÏlIWâ æ:/[EMAIL PROTECTED]>Ö¸m¶ ¾ ^l°öðÙ7°ø`o ûâÕPá CUX¬× ©ÎÄÜX» ÿÈ]Å »Vö6ÓUÇ}£ üLK§Ö"Nâó° &¾ (Î*îu-Î/ãâ0ã5n7~ 9N ;Nþ=À äB~ Dnä¿ä äÈÀäNàä÷ å, [EMAIL PROTECTED]>æ-ÆLâ c!Pr%Aò=Û WÍá)¤8;̤»õOδ¡¨XÑF [EMAIL PROTECTED] ··lÊÈLtu:ªkÅ £ªX»Õ0°uË \GWà 0ôÙ¹¬ ÌCèW Φ Càʦ¾n ¡>[EMAIL PROTECTED] ñê±Þ³^ë¾pë¹¾ë½þëjìÃ~Å~ìØìËîÍþìíÓ Õ~íÔíÛ^ÝþímîÅ0îmPîT4ã È$ÙQþ:[EMAIL PROTECTED],ÚIEÐUÿD v`»U· p¶ ɦt [EMAIL PROTECTED] ;2= /ò¾UòpòA+_.ó"ó46óÈ óÀó%àóx ôù)ô5oFßH¯ôÀôNO P_ìÆÎUïÍW¿¦Y¿õvÐõðõwöÅ0öpegÏÆ4ì§yæÛ`$M/CÌrÓåÓµêóÌL\ÇOÇðOà6À¦ü[ pµMep0Ú¤]uþà0|[EMAIL PROTECTED] IèÇ° _ ò¡Ì[ÿ~Ä®õ=YÄ·aÚk_¸"rµF¿rwcÛ&ä·EKª±BÿÔ Q¢ *U'qâ~õéãÇÏ«W%$¡[^¼hÑ+/'NlØhÓ¦> 3Z¸ðÀ^¸páÁ)¼jÕVÂYªX±? aÃVOi=xM>mºnݹqã*7o^<<È1°GbÅÒÊ]=wî*}»Tª7o½zµHÐ B BHÑ"F=IÒ$J,]JsfÍ9wöüthÑUG.þm ïéè¦â A{/]:eʬXáB62b*DhÑ£G;v,ãÆ/MlÙâÆMÂRHuãyñ+0`)ºÐÖ[vïÜqqâÀ!Cð°ÄÉïßO~ùQºp¥ ¾*%ΠŪÂË7 MC7ÕXs ¶Ùh³ 7Ýxð)à+¬¸ã[.!çÈNº<¨³»b´ãÎ;ðÄ#Ï<ôðP½öÞOù껯üöã¿ÿ [EMAIL PROTECTED] 1Ä°k(U¾øþ0(Âðh Ô;8 H=;Tªi Äk:g¨Óv¬Gª| H!TÊÈtTI'¡)*l+Ë-»ü2Ì1})óLhÒ\³Í7ã,fÎ:ïÌsÏ"ú,[EMAIL PROTECTED] öPNeÔQH% RK# ªùzæs´Òº#\2t¥âyJy®l¨'kæP-tÐa%JÎ95Ö8$ßC r(;9 òb PÈ3¢aõÀ!U S©ÞZ'´Þ Ýø©jUQ庰ç2Èxâ V^¹(Éå^©ÖùX[¦&HºÎ1S76«þ/Ìwùå0Ãd JN ò>©nT=õfOZ¨ÒuÚ ·(ÍÊh©°f½!ÙdUfY}¹)¥ªùæ©Ù¹gr~¡>¤>¸§Ú©©¶Áê«Ïzkº ljÄîìÍîÑì§l±e¢¢?ù$_åܨ¢ ±Ë®p±ÑIhØ8;·¹:aåØq¤Jý Üêl0ÁÆMPOa«É©ÒĹsßÒxãÐ/å±cÒM/u_Tÿ u×Úk¿=wHvï½ßßÂð§ã"yË]þ÷¼èzÖ£ÁI°5l¯ÝÍ÷Â7¾ÞÏGèaµá([EMAIL PROTECTED] ¢/Ü°¤=8Ù'¸¤5¤?áNðéA `#èW¸ }ÜÔn`0í1ÓSOÃútGYJ*¶[ :ÎB.¦í#´F OÂæ« |x!b8öá«È!NxHQ $¢D«)t"Y EPÑV\µØ±.6Ò7ô Ç4B/HiCcLPÄ"V¯ÊAJCaûëxÊ»àGT Ô .Ø<±DSÈ ª§>)[EMAIL PROTECTED]<«vYHÔáHfú¦-J wfb¦z¤ 8