mod-proxy

Apache websocket redirection to Tomcat: mod_proxy and mod_proxy_wstunnel

风流意气都作罢 提交于 2019-12-06 12:27:40
I am trying to redirect traffic from Apache to Tomcat by using mod_proxy and mod_proxy_wstunnel modules. HTTP traffic is redirected without problems but I am not able to successfully redirect websocket traffic with any configuration I tried so far. I am using Apache 2.4.28 and Tomcat 8.5.13 I must say when I use Tomcat without Apache, websockets works perfectly fine: The Tomcat connector that works for this configuration is next: <Connector URIEncoding="UTF-8" compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript" compression="on"

Mapping a subdomain to a Servlet context using Apache 2.x and Tomcat 6.x

荒凉一梦 提交于 2019-12-06 07:10:50
问题 I have installed Archiva on my machine under Tomcat 6.x at http://dev.mycompany.com:8080/archiva and can access the application and everything, but I want to access it from the subdomain archiva.mycompany.com . I have Apache 2.x running on port 80 and using Virtual Hosts and mod_proxy to route from other subdomains to the other various services I am running on this machine. I now want to create a subdomain archiva.dev.mycompany.com and point that to dev.mycompany.com:8080/archiva . I can't

Locally 401 Working, Staging Server getting a 302 instead

半世苍凉 提交于 2019-12-06 06:42:17
问题 I'm probably not going to get all the required info needed to help the first stab but I'll do the best I can and edit this as we go along. I've got a Grails 1.3.7 application using Spring-Security-Core plugin. I'm working on code that deals with session timeouts and ajax requests. In the LoginController, I have the following: def authAjax = { session.SPRING_SECURITY_SAVED_REQUEST_KEY = null response.sendError HttpServletResponse.SC_UNAUTHORIZED } In a global JavaScript file, I have the

Setting up mod_proxy_html on CentOS 7

家住魔仙堡 提交于 2019-12-06 04:14:01
I'm trying to do some testing on my web server to make sure reverse proxy is working as expected before putting it on a live environment, but I am running into some problems with mod_proxy and mod_proxy_html. I have 2 virtual hosts, 1 on port 80 and 1 on port 8080. My goal is to have incoming requests for www.example.com/path/ to come in on port 80, and get reverse proxied to port 8080. Here are my virtual host settings: <VirtualHost *:8080> ServerName www.example.com:8080 DocumentRoot /var/www/html/test RewriteEngine On RewriteCond %{REQUEST_URI} !^.*test RewriteRule ^/?(.*) http://127.0.0.1

ProxyPass and ProxyPassReverse for Django app

99封情书 提交于 2019-12-06 03:20:12
I have a follow up question from my original Django serving question which was how to develop Django apps and serve them from the same server as my main PHP-based site (all part of a larger migration of my website from a static and PHP driven one to a series of Django apps). I couldn't quite use the name server solution I was provided with, and instead just deployed my Django applications on a different port (8000) using mod_wsgi. Now, however, I need to actually integrate the Django application into the main site. In my Apache 2.0 configuration file (for say http://www.example.com ) I added

web apps on localhost on different ports accessed via port 80

白昼怎懂夜的黑 提交于 2019-12-06 01:37:46
On my laptop, with Apache I have different web apps in various directories on my laptop, that I can start using simple webservers listening on different ports. For example ~/app1/./app.pl >> listening on http://localhost:3000/ ~/app2/./app.pl >> listening on http://localhost:3001/ ~/app3/./app.pl >> listening on http://localhost:3001/ I want to access the above from my browser like so http://localhost/app1 http://localhost/app2 http://localhost/app3 Can I do the above with mod_proxy? If so, how? Update: I must add that I have Googled for mod_proxy, read the tutes on Apache's website, and

Mod cluster proxy timeout in apache error logs

半世苍凉 提交于 2019-12-05 10:42:46
In our environment we get these entries consistently in error logs. [Sun Dec 22 20:29:43 2013] [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header [Sun Dec 22 20:29:43 2013] [error] ajp_read_header: ajp_ilink_receive failed [Sun Dec 22 20:29:43 2013] [error] (70007)The timeout specified has expired: proxy: read response failed from (null) (xx.xx.xx.xx) [Sun Dec 22 20:30:01 2013] [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header If these errors appear from all nodes at once the site will be throwing a 998 response

WebSphere Portal behind reverse proxy and getServerPort()

与世无争的帅哥 提交于 2019-12-05 04:41:25
问题 I have problems accessing WebSphere Portal which is deployed behind reverse proxy (using Apache). The problem is that while inspecting HTTP requests issued by browser, some requests are targeted at proxy, and some directly at WebSphere Portal. My Apache configuration: ProxyPassReverseCookieDomain backend-server proxy-server ProxyPass / http://backend-server:10039/ ProxyPassReverse / http://backend-server:10039/ The problem is, some generated resources contained absolute URIs targeting at

Can stand-alone Jetty be used as a reverse proxy (without Apache mod-proxy)

限于喜欢 提交于 2019-12-05 04:37:34
I have an application which includes a Jetty web server that we distribute to multiple user to deploy on their servers. Based on some new requirements, we need to include reverse proxy capabilities. The Jetty documentation talks about using Apache as the reverse proxy in front of Jetty. While this works, it would be much easier to just use Jetty and not have to carry around Apache. Is there any way to configure standalone Jetty as a reverse proxy? Sure you should be able to use the ProxyServlet which is fully async and quite customizable if needed: http://www.eclipse.org/jetty/documentation

Apache mod-proxy ProxyErrorOverride for specific URL patterns

喜夏-厌秋 提交于 2019-12-04 17:27:07
问题 I am using Apache 2.2 with mod-proxy and I have configured it with several ProxyPass statements to proxy from remote URL to local URL. I need to have custom error documents returned from Apache for these proxied URLs so I set "ProxyErrorOverride On" in my mod-proxy configuration along with some ErrorDocument directives (with local URL path) to return custom error pages for a few HTTP status codes of interest. However, when a status code is returned for which I have NOT created an