Symfony without Apache server? - apache

I just read this page saying that Apache is being deprecated and won't be supported in Symfony3. Is the process detailed on this page for if you're remapping 'old' projects that use apache web server to use the PHP web server? Or is this the 'deprecated' information that we shouldn't be using going forward?

You should read them carefully. Not Apache is deprecated Apache Router is deprecated. Apache is the Webserver and "Apache Router" is a component. So you can use them in SF3.

Related

How to get disp_apache2.4.dll for Apache 2.4 version for AEM

Recently I have installed Apache Http server 2.4 but I need disp_apache2.4.dll. I have gone through number of forums but no luck. Please suggest me some links or forums to get that dll file.
Note : I am using Adobe CQ (AEM)
Only "Dispatcher for Apache HTTP Server 2.2" is available for IIS on Windows. Dispatcher for Apache HTTP Server 2.4 is not supported and therefore the version you are looking for is not available on this platform.

JIRA Issue/Filter Macro in Confluence generates invalid link

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 can add a new module in Apache Http server, Can i do the same in IBM Http Server (IHS) as it uses the apache http server underneath?

I have this requirement to write a customized module in http server. Newer version of the application uses the APACHE http server and the older version is deployed on IHS (IBM Http Server). I tried googling it but I couldn't find anywhere if I can write a module and packaged it in IHS .Is that possible ? If yes , how ? Do I have to get the code and build it with my module or I can write some extension and plugin into IHS. anything will help , thanks.
Yes, you extend IHS the same way you extend a vanilla Apache HTTP Server module -- with the Apache HTTP Server API.
You can either use binary modules compiled against vanilla Apache, or compile directly against IHS with the inclued bin/apxs script.
For pointers, look at any existing module in the core distribution of Apache, or Nick Kew's Apache Modules book.

Apache module supports in wsman profile

I want to know which all modules in apache server supports wsman profile completly?
Have mod_wsman module for configuring openwsman web service in apache.
You can download source code from this link .https://github.com/Openwsman/mod_wsman
make , install and configure it in apache.
mod_wsman is openwsman-server but without the http stack.
It's an Apache plugin, so you can use the Apache http stack to handle
requests and pass them to the openwsman-server backend for processing.
mod_wsman is not very well maintained.
Assuming by wsman you mean WS-Management...
Of the standard modules that ship with Apache Web Server (httpd). None.
Apache Tomcat also has no support for this.

How to configure apache to proxy requests

I want to add a javascript based chat system to my web app. I have read in many places that apache needs to forward(proxy) the requests to the xmpp chat server.
From what I have understood , I either need to add proxying support to apache server
OR use the jabberHTTPbind servelet.
I am trying the first thing. Add proxy support to apache. Now within Eclipse I am using Tomcat 7.0. I think this Tomcat comes with its own web server and is not using Apache. Is that true ?I am using Tomcat from http://tomcat.apache.org/download-70.cgi and added server in Eclipse by providing its extracted path.
I am not able to find any apache related folder structure eg(/etc/apache2/apache2.conf) within my Tomcat extracted directory.Also can't find httpd.conf anywhere .
Should I need to download apache separately and connect my tomcat to it.
I think adding proxy support to apache is required because javascript code won't be able to connect to any URL other than the current domain. so the question again is the same , where are all these apache2.conf and httpd.conf to add mod_proxy. and where can I do the virtual host mapping.
Any help to move ahead with be very much appreciated.
You need to install the Apache HTTPD server and enable reverse proxying. Read the doc on mod_proxy on how to do this. There are tons of resources on Stackoverflow as well; search for Apache reverse Proxy. The conf files you mention are part of the Apache HTTPD install.
javascript code won't be able to connect to any URL other than the current domain
That is generally true unless you enable CORS