This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Web filtering kills the speed of an AWS RDS application

I am having an issue with Web Filtering and an RDS application hosted in AWS on a UTM9 SG105 with Firmware version 9.210-20. I added everything I could find for AWS servers and IPs into a whitelist exception, but whenever I turn Web Filtering back on their application starts to crawl. Times basically double for all actions. Is there any specific settings I need to enable in web filtering to make it exclude all RDS applications from scanning?

This thread was automatically locked due to age.

Parents

0 DanIronlogix over 10 years ago

Firmware is now updated, still having the same issues. I double checked the DNS Best Practice settings, our config was fine. We filtering is in transparent mode. The attachment is the screenshot is of the exception from web filtering.

I believe this is the applicable log. If the time is measure in microseconds then the fulreqtime seems pretty absurd. I can't find any documentation as to what unit of time it is measured in though.

2015:04:13-12:00:06 removed httpproxy[3782]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="CONNECT" srcip="local ip" dstip="public ip" user="" ad_domain="" statuscode="200" cached="0" profile="REF_DefaultHTTPProfile (Default Web Filter Profile)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="3763284" request="0xe3ce7000" url="us-std-00001.s3-external-1.amazonaws.com/" referer="" error="" authtime="0" dnstime="9" cattime="0" avscantime="0" fullreqtime="112070431" device="0" auth="0" ua="" exceptions="av,auth,content,url,ssl,certcheck,certdate,mime,cache,fileextension,size,patience"
- Capture.PNG
- View
- Hide
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 DanIronlogix over 10 years ago

Firmware is now updated, still having the same issues. I double checked the DNS Best Practice settings, our config was fine. We filtering is in transparent mode. The attachment is the screenshot is of the exception from web filtering.

I believe this is the applicable log. If the time is measure in microseconds then the fulreqtime seems pretty absurd. I can't find any documentation as to what unit of time it is measured in though.

2015:04:13-12:00:06 removed httpproxy[3782]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="CONNECT" srcip="local ip" dstip="public ip" user="" ad_domain="" statuscode="200" cached="0" profile="REF_DefaultHTTPProfile (Default Web Filter Profile)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="3763284" request="0xe3ce7000" url="us-std-00001.s3-external-1.amazonaws.com/" referer="" error="" authtime="0" dnstime="9" cattime="0" avscantime="0" fullreqtime="112070431" device="0" auth="0" ua="" exceptions="av,auth,content,url,ssl,certcheck,certdate,mime,cache,fileextension,size,patience"
- Capture.PNG
- View
- Hide
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data