Apache Mod_proxy 500 Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn apache proxypass 500 internal server error more about Stack Overflow the company Business Learn more about hiring developers or posting 500 internal server error reverse proxy ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack
No Protocol Handler Was Valid For The Url
Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Application error passthru when using apache mod_proxy up vote 2 down
Https: Failed To Enable Ssl Support For
vote favorite Heyas. I'm using mod_proxy with apache2 provide vhost ability to multiple servlet apps running on the local machine. It works fine, for the most part. Requests come into apache then are directed to the application bound on a port on localhost. The app receives the request and responds, which is delivered back to the client by apache. The problem I'm having is that the application delivers mod_proxy_http 500's on errors, and mod_proxy stomps on them. Often these errors are caused in a ajax request and the error is handled in client side javascript. For example, a call to a server side createObject(name) might throw a NameNotUniqueException , which is delivered back as a 500. The client javascript might then display an appropriate error message. When an error is thrown by the application (resulting in a 500 response to mod_proxy), then apache stomps the error message and returns 500 Internal Server Error Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. .. the stock apache server side error message. I want mod_proxy to pass the original 500 back through to the client. Is there a directive I've missed which prevents clobbering of the 500? TIA apache mod-proxy share|improve this question asked Mar 28 '10 at 4:26 Andrew Taylor 52869 What about using mod_proxy_ajp or mod_jk? Seems to me they are more tailored to connecting Apache to servlets. –Jackson Miller Mar 28 '10 at 5:51 good suggestion. The app is a standalone jetty powered dyn web engine. Perhaps I should look at jetty ajp connections. –Andrew Taylor Mar 28 '
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring
Sslproxyengine
developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask proxypass https Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join 500 proxy error them; it only takes a minute: Sign up Issues Setting up a reverse proxy in Apache up vote 7 down vote favorite 3 My roommate and I each have a separate webserver we are trying to set up. We http://stackoverflow.com/questions/2531895/application-error-passthru-when-using-apache-mod-proxy are trying to use mod_proxy so that his server will forward requests to my machine (we have two seperate machines behind one router) based on the server name. I've given the basics of what we have in our apache config currently but we are getting a 403 Forbidden error when trying to access the second domain (the first, www domain, works fine). NameVirtualHost *:80
Login: [x] First Last Prev Next This bug is not in your last search results. Bug50630 https://bz.apache.org/bugzilla/show_bug.cgi?id=50630 - Apache return 500 error with authentication by LDAP secure port (ldaps) https://www.apachelounge.com/viewtopic.php?t=6256 Summary: Apache return 500 error with authentication by LDAP secure port (ldaps) Status: NEW Product: Apache httpd-2 Classification: Unclassified Component: mod_authz_ldap Version: 2.2.13 Hardware: PC Linux Importance: P2 normal with 3 votes (vote) TargetMilestone: --- Assigned To: Apache HTTPD Bugs Mailing List URL: Keywords: Depends on: Blocks: 500 internal Show dependency tree Reported: 2011-01-21 08:36 UTC by Ignasi Modified: 2014-05-30 07:08 UTC (History) CC List: 3 users (show) bugs d.george Scott.A.Hendrickson Attachments Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this bug. Description Ignasi 2011-01-21 08:36:03 UTC We have Linux RHEL6 with httpd 500 internal server 2.2.15, and after loged with LDAP username and password, apache return 500 error. Return this error only if you use ldaps (port 636), for ldap (port 389) works fine. No information available about this error in the server error log. With the follow configuration: # vim: syntax=apache
contribution towards the costs, the time and effort that's going in this site and building. Thank You! Steffen Apache Lounge is not sponsored by anyone.Your donations will help to keep this site alive and well, and continuing the building of the binaries. mod_proxy : error page handling Apache Forum Index -> Apache View previous topic :: View next topic Author Message rsinklairJoined: 10 Nov 2014Posts: 2Location: UK Posted: Mon 10 Nov '14 20:03 Post subject: mod_proxy : error page handling hi all, a question on mod_proxy : We're using mod_proxy as a simple reverse proxy (ProxyPass & ProxyPassReverse) to reverse-proxy various back-end PHP and Mono/.NET apps. One problem we see is that when the back-end PHP app suffers an error (e.g. a 404 or 500) , then mod_proxy ignores the nicely-formatted custom error page served up by our PHP app, and instead serves a very plain generic mod_proxy 404 or 500 error page back to the client. Is there a way to configure mod_proxy to serve up the 500/404 error page content which is created by the back-end app ? ( We thought ProxyErrorOverride might help, but it seems to be intended for the opposite scenario, where I want to *ignore* the 404 page content from the back-end and show a mod_proxy-defined error page instead. We're using apache 2.2 on 64-bit CentOS 6.5 ( httpd-2.2.15-31.el6.centos.x86_64 ) Config like: ... ProxyPass /abc/ http://server4/abc/ ProxyPassReverse /abc/ http://server4/abc/ thanks Rob London, UK Back to top rsinklairJoined: 10 Nov 2014Posts: 2Location: UK Posted: Tue 11 Nov '14 19:08 Post subject: update - we discovered we had 'ProxyOverride On' set elsewhere in our apache config , so looks like this was a self-inflicted problem ! *doh* Back to top Apache Forum Index -> Apache Page 1 of 1