502 Proxy Error The Request Is Not
Contents |
clients behind ISA Server 2006 ★★★★★★★★★★★★★★★ Ori Yosefi - MSFTMay 24, 20103 0 0 0 Consider a scenario where users who are part of the internal network of the ISA server and have configured
502 Proxy Error Apache
their machines as web proxy clients. When those users are trying to go to certain 502 proxy error dns lookup failure websites they get error "502 proxy error, the request is not supported (50)" message and they are not able to view the 502 proxy error apache error reading from remote server page. Data collection to resolve the issue In order to troubleshoot this type of issue, we need to run ISA data packager in repro mode using the Web Proxy and Web Publishing template. The goal is
502 Proxy Error Reason Error Reading From Remote Server
to gather data while the client workstation is having this problem. Data analysis In the ISA Logs collected with ISA data packager we see failed connection attempt with result code as 50 as highlighted below (copying only the most relevant part of the log with action and result code). Failed www.contoso.com GET 50 http://www.contoso.com/abc/xyz.html http Domain\user1 In the network traces taken on the external NIC of the ISA server we can see
502 Proxy Error Openshift
that the http get request is going out as follows with all the headers and their corresponding values in the request sent. We need to compare the response that the web server sent for this request which is as follows: In the response, we can see all the headers and their corresponding values; the important header field that was missing in the request sent by the ISA server was “ContentEncoding” which is present in the web server response with value “gzip”. By default ISA server would send this header with values as gzip and deflate but in this case it is not sending that. To find out why ISA server is not sending this header information in the request we need to analyze the BPA report. ISABPA -> add-ins section -compression filter and verify if compression filter is disabled. Following is the output from the ISABPA when it’s disabled: Compression Filter Name =Compression Filter Version =4.0 Vendor =Microsoft (R) Corporation Description =Enables HTTP/HTTPS compression Enable this filter =False Direction =fpcFilterDirectionBoth Order =4 Relative Path =comphp.dll Priority =fpcFilterPriority_High Vendor Parameters Sets = PersistentName ={8EA49FDD-FFDC-4190-8A66-724BB0342F9F} Guid ={8EA49FDD-FFDC-4190-8A66-724BB0342F9F} Resolution In such a scenario where compression filter is disabled and web server in its responses send contentencoding
VSE ePO General Google Chrome OS Uncategorized UPS Backup Exec ← Not so muchresting… Active Directory Certification Authority not 502 proxy error chrome renewingcertificate → Error Code: 502 Proxy Error. The request is not
502 Proxy Error Web Service
supported.(50) September 17, 2009 Leave a comment As referenced in my last post, I had a problem 502 proxy error apache reverse proxy with viewing a website. Whenever someone tried to view the site at work they got "Error Code: 502 Proxy Error. The request is not supported. (50)" The error https://blogs.technet.microsoft.com/isablog/2010/05/24/error-502-proxy-error-the-request-is-not-supported-50-while-trying-to-access-websites-from-web-proxy-clients-behind-isa-server-2006/ is coming from Microsoft ISA Sever 2004, to fix this you need to enable the compression filter in ISA Server 2004 Configuration > Add-Ins > tab Web Filters > properties Compression Filter > select Enable This filer. > Ok > Apply. This not only fixed the 502 proxy error but also an issue with pages appearing "stripped https://restingsysadmin.wordpress.com/2009/09/17/error-code-502-proxy-error-the-request-is-not-supported-50/ down" ie only text, no images. Share this:ShareFacebookTwitterGoogleLike this:Like Loading... Related Filed under ISA Sever 2004 Tagged with ISA Server 2004, Microsoft About Phill McSherryPhill McSherry has been working in the Australian IT industry for over 20 years and is the technical manager and solutions architect for managed services provider Titan Solutions - www.titansolutions.com.au Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. RSS LinksRSS - Posts Twitter I just supported How to Prepare for Emergencies on @ThunderclapIt // @Cryptozoic thndr.me/FsrLEs 2monthsago I'm entered to win Loot Crate's Crate-a-Day Giveaway! lootcrate.com/crate-a-day-gi… #lootcrate #giveaway 2monthsago #lfgsyd Forbidden Island https://t.co/SLMofgiIaL 2monthsago I unlocked the I
502 Proxy Error Whenever an ISA or TMG server throws a 502 Proxy Error your way, you know you are probably in http://www.chicagotech.net/msapps/isa1.htm for a real hurdle. But with a little familiarity with what a 502 error means, and how it can be fixed, you will be back in business in little time. First, lets take a http://www.tech-archive.net/Archive/Windows/microsoft.public.windows.server.sbs/2007-05/msg02120.html look at the definition of 502 HTTP response code: 502 Bad Gateway The server was acting as a gateway or proxy and received an invalid response from the upstream server. Pay close attention to 502 proxy what that is saying. The proxy (meaning your ISA or TMG server) received an invalid response from the upstream server (implying that the internal webserver that you are publishing!). Unfortunately that is not always the case as ISA and TMG can throw that error when they are unhappy about something that a normal browser would readily accept. They can also throw one of several different kinds of 502 proxy error 502 depending on the circumstances. Understanding is critical to a quick resolution. Dont just stop reading at 502, check the rest of the response. Here is how to determine whether the problem is with your ISA/TMG, or on the internal server: 1. Open a browser on the internal network. 2. Access the URL in question. 3. If you can view the content successfully, the problem is with your ISA/TMG. If not, the problem is with your webserver. Since this post is about ISA and TMG, lets assume you are able to view the content internally just fine, so well keep discussing ISA/TMG. 4. Go to your log viewer. In ISA that is Monitoring, or in TMG that is in Logs & Reports. 5. Edit the filter to look at live logs and have the user try again, or filter on the time range to see the error. Add the Filter by criteria for HTTP Status Code, and set it equal to 502. 6. Run the query, and examine the results. Some of the frequent causes of ISA/TMG generating 502s are: A 502 can be thrown by the ISA/TMG when content filtering is enabled and something in the response
time" -- does this apply to the section where there might be "incompatibility between web site and ISA's web proxy filter" and you give me steps on that? I would like to try that while people are still online, but don't want to mess things up with the changes...it is hard for me to be here when nobody is online... jared On Mon, 14 May 2007 07:19:25 GMT, v-terliu@xxxxxxxxxxxxxxxxxxxx (Terence Liu [MSFT]) wrote: Hello Jared, Thanks for posting here. From the description, I understand that you cannot browse certain internet web sites thru ISA 2004 and get error "502 proxy error". If I am off base, please do let me know. Based on my experience, the problem may occur if there is some specific access rules deny the traffic to some certain web sites. I suggest that we try the following steps to see if the problem can be resolved: 1. You have to rerun the CEICW to make sure your SBS 2003 server have right network configuration. Go through the follow KB and Rerun CEICW again carefully. How to configure Internet access in Windows Small Business Server 2003 http://support.microsoft.com/kb/825763/en-us Then open ISA 2004 console, locate on "SBS internet access rules", move this rule to the top and click Apply to save all the settings. 2. Then please open the ISA2004 Management Console, in the left panel, expand to Configuration->Networks. Under "Networks panel", double click "Internal". Switch to "Web Proxy" panel, click "Authentication" button and then uncheck the "Require all users to authenticate" option. Then click the Apply button to save the changes. 3. Please also try deleting the ISA cache to ensure there is no corrupted content. a. On the ISA Server computer, stop the Microsoft Firewall service. To do so: 1). Click Start, click Run, type services.msc in the Open box, and then click OK. 2). Right-click Microsoft Firewall, and then click Stop. b. Start Windows Explorer. c. Locate the Urlcache folder. d. In the Urlcache folder, locate the file that has the .cdat file name extension. e. Right-click the .cdat file, and then click Delete. f. When you are prompted to confirm the removal of the .cdat file, click Yes. If you are prompted to delete the .cdat file because it is too big for the recycle bin, click Yes. g. Restart the Micr