Re: [EsiGate-users] long-polling in esigate 4.1 problem

[Francois-Xavier B. <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
>
>