cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
wwong
Level 7
Report Inappropriate Content
Message 1 of 3

Problem streaming big POST

Jump to solution

I am totally new to MWG and we are facing a customer who use MWG as a forward proxy. The client application will perform big POST and with tickling bytes. It looks like MWG will not flush until the entire request as arrived the gateway. I need help on 2 questions:

1. Is there a way to lower the inspection requirement and specify maximum latency on flushing bufferred data?

2. If the app is using HTTPS instead of HTTP would that automatically resolve the streaming issue?

Thanks for helping.

1 Solution

Accepted Solutions
asabban
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: Problem streaming big POST

Jump to solution

Hello,

you should be able to play around with the Data Trickling Settings, to see if this helps to resolve your problem. Basically MWG will send only very small chunks of data to the remote end, while it is waiting for the transfer from the Client to complete. If the Web Server expects more data you can probably have success with changing the Data Trickling rates.

If you use HTTPS MWG will decrypt the traffic and you will see the same issue. You can configure MWG to NOT open HTTPS traffic, in this case the data will be moved from the Client to the Web Server without trickling, but you won´t be able to apply filtering on the transferred data.

Best,

Andre

View solution in original post

2 Replies
asabban
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: Problem streaming big POST

Jump to solution

Hello,

you should be able to play around with the Data Trickling Settings, to see if this helps to resolve your problem. Basically MWG will send only very small chunks of data to the remote end, while it is waiting for the transfer from the Client to complete. If the Web Server expects more data you can probably have success with changing the Data Trickling rates.

If you use HTTPS MWG will decrypt the traffic and you will see the same issue. You can configure MWG to NOT open HTTPS traffic, in this case the data will be moved from the Client to the Web Server without trickling, but you won´t be able to apply filtering on the transferred data.

Best,

Andre

View solution in original post

wwong
Level 7
Report Inappropriate Content
Message 3 of 3

Re: Problem streaming big POST

Jump to solution

Thanks Andre,

Our customer verifies that using HTTPS solves the stream problem of the trickling big POST.

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community