My web application runs on https with http1.1 protocol. It was built using php5.4.27 and mysql5.0 and running on apache 2.2 in Centos 6.5 32bit system.
I want to upgrade the request protocol to http2 from http1.1 with https.
I would like to know the process for updating to http2 and supported versions for php & mysql
This is handled by webserver not PHP or MySQL.
Your current version of Apache (2.2) doesn't handle HTTP/2 - only Apache 2.4.18 and above (but would recommend latest version as this is changing quite a bit and is still marked as experimental). Note there are quite a few differences between Apache 2.2 and 2.4.
An alternative, if you don't want to upgrade, is to stick a CDN with HTTP/2 support in front of your site. Some of them (e.g. Cloudflare) even offer free tiers with HTTP/2 support.
Related
Can we have an OSS instance of elasticsearch with SSL/https?
I tried this solution, but likely we will need an x-pack that is not available in OSS.
The idea is to have just SSL working in HTTPS, no Authentication required (for testing HTTPS client purposes only)
The security features in elasticseach are not included in the OSS version, only in the versions that uses at least the Basic free Elastic License.
To use HTTPS in the OSS version you will need to have a proxy in front of your nodes, like HAProxy and NGINX.
I have an Ubuntu 16.04 server with ISPConfig 3.1 and a website where I installed WHMCS.
My goal is to use this module that integrates WHMCS with ISPConfig 3.1 allowing the automatic creation, termination, suspension, and un-suspension of accounts.
But I'm kind of confused.
Is it ok to install WHMCS on a webiste from the own server to be managed (e.g. for client2, site2), or do I have to install it somewhere else? If so, where exactly?
If you're testing it should be ok to install WHMCS on the same server.
But for production, it is better for performance and security to install WHMCS on separate server or hosting.
Recently I installed SonarQube 6.1 version and I used Apache to enable HTTPs, now i am able to connect to SonarQube using both the URL's below.
Any idea how to disable the HTTP and make only HTTPs work ?
HTTPs URL = https://<SonarServer>/sessions/new
HTTP URL = http://<SonarServer>:9000/
According to your URL, the web front server and Apache are installing on the same host. So you just need to configure SonarQube to listen on localhost (in sonar.properties sonar.web.host=127.0.0.1) and configure Apache to do the reverse proxy for 127.0.0.1.
Well there are two approaches which you can try:
Approach, make sonar https (http://docs.sonarqube.org/display/SONARQUBE52/Running+SonarQube+Over+HTTPS)
based on the link above you could easily set sonar to https, instead of http - just be sure to provide a certificate etc.
you could as https://stackoverflow.com/users/2435199/eric-hartmann described, just simply bind it only to localhost
block 9000 from outside ips via firewall!
Imho i would stick with 1 or 2 depending on the time you would like to spend on that issue!
What is the difference between Apache HTTP Server and Oracle HTTP Server. What are the advantages/disadvantages of using Apache server , Oracle HTTP Server? Any insight into it is really appreciated.
Thanks,
Narendra
It's helpful to know that Oracle HTTP Server (OHS) is the Apache HTTP Server (Apache). Specifically OHS is Apache 2.2.22 including critical bug fixes from higher Apache versions. https://docs.oracle.com/middleware/1213/webtier/HSADM/intro_ohs.htm#HSADM102
* This has been updated with OHS 12.2.1 now to Apache 2.4.
https://docs.oracle.com/middleware/1221/webtier/administer-ohs/whats_new.htm#HSADM1277
OHS includes the WebLogic Server Proxy plugin (mod_wl_ohs) which brings frontend hosting to WebLogic application servers. OHS also includes configuration from the Fusion Middleware Control. Aside, this is of dubious value because you'll be editing the httpd.conf file through the advanced server configuration pages. An additional plus on the OHS side is all of the scripts and setup are generally in one place so there's less assembly of different bits such as with Apache. Finally, the control of OHS rests with the NodeManager daemon (usually) so that's one place to control WLS "Machines".
Bottom line OHS: OHS is a kinder-gentler way to be introduced to a slightly older version of Apache if you don't know Apache well. WLS plugins are included and if you're a WebLogic admin the Oracle docs are better. OHS is licensed by Oracle so it's not necessarily free, certainly not for support.
So to Apache's advantages. Since the mod_wl_ohs plugin can be downloaded separately, it can also be incorporated in an Apache installation. The configuration of the plugin is as involved as "normal" Apache httpd.conf edits, which is to say above-average complexity for those who have never worked with Apache HTTP Server. The server is also controlled from either init.d or systemd directly, as opposed to being controlled by nodemanager (which in turn is controlled by init.d/systemd).
Bottom line Apache: If you're a sysadmin who has already invested a lot in Apache, adding the WLS proxy plugin is pretty straight forward and you've gained everything OHS has to offer. But you'll have to kit it together yourself if you're a WLS administrator. Apache is licensed under the Apache 2.0, which is sort of a way of saying it's "free".
I will kindly direct you here.
Its also important to note that if you maintain a valid support contract with Oracle and you user their HTTP server they will support that tier as well. So its another way you can lump as many products as you can into a support contract.
I have Apache server 2.2.15 on my Windows 7 machine and I want to run Bench on a server I have using https. But when I run ab [myopts] https://example.com, I get SSL not compiled in; no https support. From what I've read you can compile ab with https support with a flag during the server install.
My question is, considering I already have server installed, what is the easiest/best way to benchmark my server over https?
Use the abs.exe tool to test sites with a SSL cetificate