I use mod_spdy to realize SPDY on apache. But I met some problems.
I did every step on ubuntu according to Google's document of installing mod_spdy.And I realized https on Apache. When I checked if mod_spdy has worked, I sent https request to the server, but I donot see server's domain listed in the "SPDY session" table that means the mod_spdy don't work. I also checked Apache server logs, and I didn't find any error message from mod_spdy.
I hope somebody can help me to deal with this problem.
Related
The setup:
Ubuntu 16.04
JIRA Software 7.03 (on port 8080)
Confluence 6.03 (on port 8090)
NGINX 1.10.0 as a reverse proxy to...
Apache 2.4.18
The problem: Whenever I try to embed a JIRA issue into a Confluence page via the built-in JIRA Issue/Filter macro, the issue is successfully located and its status is successfully listed. However, the link from the Confluence page to the actual issue in JIRA points to localhost:8080.
As per the suggestion in Incorrect Links in JIRA Issues Macro (cause #1), I tried enabling ProxyPreserveHost in Apache, with no discernible effect.
Question 1: Am I even digging in the right direction, or is there some other likely cause for the issue that I'm missing?
Question 2: If the issue really is likely due to a configuration mismatch between Confluence and the web server, where should I start digging, given that I'm using NGINX as a reverse proxy?
I'm very hazy on the specifics of configuring web servers. Do I need to verify my settings in both NGINX and Apache, or just Apache (NGINX is set to pass through pretty much everything non-static)? Do I just follow the instructions for Proxying Atlassian server applications with Apache HTTP Server (mod_proxy_http)?
I haven't done this yet because I'm worried my lack of understanding will cause something to explosively decompress.
Thanks in advance!
Since you redirect to localhost:8080 and 8080 is JIRA's default port, I believe that you need to check following and most likely it's related to misconfiguration of the proxy:
Configuration of JIRA Base URL - Is it configured properly?
Do you have proxyPort and proxyName in the connector of server.xml?
What you are seeing when you navigate to Application Link configuration of JIRA and Confluence? Is is showing any errors?
I'm super frustrated and created an account just to get this solved. I've tried everything under the sun and nothing is doing any good whatsoever. Please give me the benefit of the doubt.
I have 2 configurations of Apache, one that's working perfectly fine and another that isn't. I want to make the one that isn't working work like the one that is working. The one that isn't working isn't allowing any non-localhost traffic yet came installed with wamp which I'm trying to leverage, and the one that is working is an independent install that I've configured to allow all traffic. Configuring the wamp Apache in a way that seems to me to be exactly the same is still not allowing any non-localhost traffic through
Here is the configuration file from the working Apache server:
http://pastebin.com/dQDVDA53
And here is the non-working configuration from the wamp apache server:
http://pastebin.com/geF0aLRF
Any help would be greatly appreciated. Thanks...
Hello I have seen a strange behaviour in Apache HTTPD SSL and TomEE (in fact it is a Tomcat so it is exactly the same for Tomcat), I am configuring the typical Apache as frontend and TomEE as backend solution. Currently Apache is configured with SSL and with mod_jk it connects to TomEE using AJP. This works perfectly. The problem is that inside my code I need to get the ssl session id:
String ssl = (String)servletRequest.getAttribute("javax.servlet.request.ssl_session_id");
I don't know why but sometimes this attribute is null and sometimes not. It may return a null at first then stay like 10 requests working and then stop working again during some requests and the get attribute returns null.
It seems that everything is configured correctly since sometimes works. Have you ever found something similar or knows what it can be happening? Do you think that maybe the problem is on client (browser) side?
Everything is dockerized here: https://github.com/lordofthejars/apache-tomee-ssl so you can review configuration files of tomcat and apache or even run it.
Thank you so much for your support.
Doesn't have to be Apache, but that's just the only HTTP server I know of (Actually could you guys recommend alternatives that I could look into as well?)
Anyways, so I have been messing around with Amazon Web Services and I created an EC2 server instance with an Amazon Linux Image. On that, (Following guides and examples) I installed Apache and now when I make a GET request to my public IP, it returns to me the HTML files I created on my server.
My question is, what if I never installed Apache, and then made an HTTP request to my public IP? For no reason really, the question just came up in my head and I'm curious. I'd rather not figure out how to uninstall Apache or create a new instance to figure it out, so I was wondering if somebody could weigh in as well as tell me a little more about what it is exactly apache does on a server. My understanding is that it is a layer you can install on your server OS that will create a socket listener to port 80 (HTTP), and when a request is made on that port, Apache will return web pages? Also I think I read somewhere you could configure Apache to forward a port to something like a python server script?
Thanks in advance for your time!
could you guys recommend alternatives that I could look into as well?)
nginx is a popular alternative to apache. It's much more efficient.
what if I never installed Apache, and then made an HTTP request to my public IP?
Your browser would get a "connection reset" because there is nothing on port 80. Your browser would display a message (Chrome says "This webpage is not available"). You would NOT get a "404" because that requires an HTTP server to send HTTP codes.
If your server was firewalled instead, you'd bet a busy wait for a while, then a message about the server not responding.
Also I think I read somewhere you could configure Apache to forward a port to something like a python server script?
Yes, that is called "reverse proxy" mode. It's essential to any application website if you want to scale. The web server(s) can distribute traffic to one or more backends running the application. The web server is useful for filtering bad requests (since your backend in Ruby/Python will be 1000's of times slower than the reverse proxy.)
Well, if you want to test what will happen if Apache isn't installed, you can always just stop the Apache service by typing:
sudo service apache2 stop
or
sudo service httpd stop
depending on your version. Then if you visit your site's webpage you'll get a 404 error or something similar.
There are ways to use python scripts to run simple servers, but in general it's easier to just let Apache handle that and use a framework like Ruby on Rails or Django to control the display and creation of content for your server.
I have a problem running ServiceStack as daemon on Linux.
I just started to work into creating a REST API with C# on Mono. I studied your Wiki about it and yesterday I tried to run ServiceStack as daemon on Linux (Ubuntu 13) exactly as described on the wiki page:
https://github.com/ServiceStack/ServiceStack/wiki/Run-ServiceStack-as-a-daemon-on-Linux
But I encountered a problem, tried every possible solution I found in the web, but nothing helped.. The problem:
If I access http://127.0.0.1:8080 on the Ubuntu System everything is fine and I am beeing redirected to http://127.0.0.1:8080/metadata and get the Service Metadata.
If I access http://127.0.0.1:80 I get the static content. Also fine.
BUT if I access http://127.0.0.1/api I'm being redirected to http://127.0.0.1/metadata and get a 404. Which is absolutely understandable because there is no such thing on Port 80.
You know I'm not that good in apache, but after reading the configuration mentioned in the wiki I thought this should work normally. Am I wrong? Or do you have any idea how I can solve this?
Another problem is that if i access the service on my ubuntu system from another system, e.g. Windows through http://ubuntu-dev:8080, I get Bad Request (invalid host).
I also get the 404 there if I accesshttp://ubuntu-dev/api.
I think the Bad Request Thing must have something to do with servicestack because apache only listens on port 80 (as it should I think). Do you have any suggestions about this?
It would be really nice if someone could help me because I really don't know what to do with these problems.
Greetings, daily
It might be a problem that only occurs when it runs on a different port than 80.
Probably it's not redirecting properly when a port is set.
Try running it on nginx with fastcgi (fastcgi-mono-server4), there you can run it on port 80.