Re: [users@httpd] Weird connection issues with mod_proxy_wstunnel

2015-04-15 Thread Eric Covener
On Wed, Apr 15, 2015 at 7:16 AM, Marc Hörsken i...@marc-hoersken.de wrote:
 I was unable to find any useful resources about how to do this, yet.
 Can you point me in the right direction?

 Is there some special header that needs to be sent by the server?


I would have thought this is purely a browser bug and the application
has very little influence.  Does it fail cross-browser?

-- 
Eric Covener
cove...@gmail.com

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



[users@httpd] reg: upgrade apache http from 2.2.27 to 2.2.29

2015-04-15 Thread venu thangalapally
Hello everyone,
We are planning to upgrade Apache 2.2.27 to version
2.2.29.

do i have to install 2.2.29 all new and do all configs with weblogic again
? or should i be able to install 2.2.29 in a seperate path and just copy
the required files onto already existing 2.2.27?

please suggest



Regards
Venu


Re: [users@httpd] Weird connection issues with mod_proxy_wstunnel

2015-04-15 Thread Marc Hörsken
Hello Eric,

 Am 15.04.2015 um 14:05 schrieb Eric Covener cove...@gmail.com:
 
 On Wed, Apr 15, 2015 at 7:16 AM, Marc Hörsken i...@marc-hoersken.de wrote:
 I was unable to find any useful resources about how to do this, yet.
 Can you point me in the right direction?
 
 Is there some special header that needs to be sent by the server?
 
 
 I would have thought this is purely a browser bug and the application
 has very little influence.  Does it fail cross-browser?

At first I thought so, too. But it does fail using Firefox 37.0.1 and Safari 
8.0.5 on Mac OS X Yosemite 10.10.3.

Best regards,
Marc
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



[users@httpd] httpd 2.4 and windows hangs and AcceptFilter solution

2015-04-15 Thread Andy Wang
We've come across numerous cases where apache httpd 2.4 (I'm using 
2.4.12 but I don't believe this is version specific) hang using the 
default configuration options.


There are two cases
1) we have an InstallAnywhere installer that launches httpd during 
install time to do some initial work.  When the installanywhere 
installer starts httpd.exe (it does it via cmd.exe) httpd does not 
respond to requests.  If you kill the installanywhere installer, then 
all of the sudden httpd starts responding

2) certain IE 11 client requests hang httpd 2.4.

I've wireshark'ed #2 and at some point, an http GET gets an ACK and 
nothing more.  I've peeked a little bit at the process threads with 
processexplorer (unfortunately i'm not a windows developer, so I'm not 
entirely familiar with the low level windows stuff) and everyhting looks 
like it's okay and simply waiting for requests.


What I found after googling and testing is AcceptFilter http|https none 
prevents both of those problems.  I've not yet tried connect to see if 
that works either.


But what I'm really wondering about is, can anyone explain, especially 
in #2, what it is about AcceptFilter http none that actually resolves 
these types of issues?


Thanks,
Andy

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



Re: [users@httpd] Weird connection issues with mod_proxy_wstunnel

2015-04-15 Thread Eric Covener
On Wed, Apr 15, 2015 at 12:18 PM, Marc Hörsken i...@marc-hoersken.de wrote:
 Hello Eric,

 Am 15.04.2015 um 14:05 schrieb Eric Covener cove...@gmail.com:

 On Wed, Apr 15, 2015 at 7:16 AM, Marc Hörsken i...@marc-hoersken.de wrote:
 I was unable to find any useful resources about how to do this, yet.
 Can you point me in the right direction?

 Is there some special header that needs to be sent by the server?


 I would have thought this is purely a browser bug and the application
 has very little influence.  Does it fail cross-browser?

 At first I thought so, too. But it does fail using Firefox 37.0.1 and Safari 
 8.0.5 on Mac OS X Yosemite 10.10.3.

And not sharing any proxy between browser and httpd?

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



Re: [users@httpd] Weird connection issues with mod_proxy_wstunnel

2015-04-15 Thread Marc Hörsken
Hello Eric,

 Am 15.04.2015 um 19:47 schrieb Eric Covener cove...@gmail.com:
 
 On Wed, Apr 15, 2015 at 12:18 PM, Marc Hörsken i...@marc-hoersken.de wrote:
 Hello Eric,
 
 Am 15.04.2015 um 14:05 schrieb Eric Covener cove...@gmail.com:
 
 On Wed, Apr 15, 2015 at 7:16 AM, Marc Hörsken i...@marc-hoersken.de wrote:
 I was unable to find any useful resources about how to do this, yet.
 Can you point me in the right direction?
 
 Is there some special header that needs to be sent by the server?
 
 
 I would have thought this is purely a browser bug and the application
 has very little influence.  Does it fail cross-browser?
 
 At first I thought so, too. But it does fail using Firefox 37.0.1 and Safari 
 8.0.5 on Mac OS X Yosemite 10.10.3.
 
 And not sharing any proxy between browser and httpd?

no, there is no proxy between the browsers and httpd.
The connections are using HTTPS over TCP over IPv4.

Best regards,
Marc
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



Re: [users@httpd] Apache Installation

2015-04-15 Thread Yehuda Katz
Check your PHP error reporting level and/or error log for PHP errors.

- Y

On Wed, Apr 15, 2015 at 11:13 PM, Ethan Rosenberg 
erosenb...@hygeiabiomedical.com wrote:

 On 04/14/2015 10:18 PM, Yehuda Katz wrote:

 On Tue, Apr 14, 2015 at 9:05 PM, Eric Covener cove...@gmail.com mailto:
 cove...@gmail.com wrote:

 On Tue, Apr 14, 2015 at 10:36 AM, Ethan Rosenberg
 erosenb...@hygeiabiomedical.com mailto:erosenberg@
 hygeiabiomedical.com wrote:
  [Tue Apr 14 00:51:10.502172 2015] [:error] [pid 7610] [client
 ::1:53486]
  script '/var/www/html/start.php' not found or unable to stat

 Something non-standard under /etc/apache2 or /.htaccess or
 /var/.htaccess or /var/www/.htaccess is mapping that request of
 /start.php to /var/www/html/start.php. I'd look at anything matching
 html or php in those configuration files and see what turns up.
 You should be familiar with grep -ri of configuration files.


 That looks like the standard Debian/Ubuntu configuration starting with
 2.4.
 The DocumentRoot is probably in /etc/apache2/sites-enabled/
 000-default.conf

 - Y

 

 Yehuda -

 Thank you.

 Found it!

 root@meow:/home/ethan# grep -i root  /etc/apache2/sites-enabled/
 000-default.conf
 DocumentRoot /var/www/html

 Changed that and it finds the files.

 But .

 This works perfectly

 !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN 
 http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
 html xmlns=http://www.w3.org/1999/xhtml;
 html
 head
 titleTest Connect2/title
 meta http-equiv=Content-Type content=text/html; charset=utf-8
 /
 style
 body{
 background-color: #89caeb;
 width:100%;
 height:100%;
 position: relative;
 font-family: Helvetica, Arial , Liberation
 Sans, Free sans, sans-serif;
 overflow-y: scroll;
 }
 /style

 /head
 body

 strong
 div align='center'
   h3Handle Weight/h3
 /div
 /strong



 ?php


 $hostname=localhost;
 $database=Store;
 $username=ethan;
 $password=;

 global $i;


 $link = mysqli_connect($hostname, $username, $password);
 if (!$link) {
 die('Connection failed: ' . mysql_error());
 }
 else{
  echo Connection to MySQL server  .$hostname .  successful!
  . PHP_EOL;
 }

 $db_selected = mysqli_select_db($link, $database);
 if (!$db_selected) {
 die ('Can\'t select database: ' . mysqli_error());
 }
 else {
 echo 'Database ' . $database . ' successfully selected!';
 }

 ?

 /body
 /html

 This fails...It does not even change the background color or print the
 header

 ?php
 session_name(STORE);
 session_set_cookie_params( '24000', '/' );
 session_start();
 echo 'hello world';
 ?
 !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN 
 http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
 html xmlns=http://www.w3.org/1999/xhtml;
 html
 head
 titleHandle Weight/title
 meta http-equiv=Content-Type content=text/html; charset=utf-8
 /
 style
 body{
 background-color: #89caeb;
 width:100%;
 height:100%;
 position: relative;
 font-family: Helvetica, Arial , Liberation
 Sans, Free sans, sans-serif;
 overflow-y: scroll;
 }
 /style

 /head
 body

 strong
 div align='center'
   h3Handle Weight/h3
 /div
 /strong
 ?php
 snip

 Totally Confused

 TIA

 Ethan






Re: [users@httpd] Apache Installation

2015-04-15 Thread Ethan Rosenberg

On 04/14/2015 10:18 PM, Yehuda Katz wrote:

On Tue, Apr 14, 2015 at 9:05 PM, Eric Covener cove...@gmail.com 
mailto:cove...@gmail.com wrote:

On Tue, Apr 14, 2015 at 10:36 AM, Ethan Rosenberg
erosenb...@hygeiabiomedical.com mailto:erosenb...@hygeiabiomedical.com 
wrote:
 [Tue Apr 14 00:51:10.502172 2015] [:error] [pid 7610] [client ::1:53486]
 script '/var/www/html/start.php' not found or unable to stat

Something non-standard under /etc/apache2 or /.htaccess or
/var/.htaccess or /var/www/.htaccess is mapping that request of
/start.php to /var/www/html/start.php. I'd look at anything matching
html or php in those configuration files and see what turns up.
You should be familiar with grep -ri of configuration files.


That looks like the standard Debian/Ubuntu configuration starting with 2.4.
The DocumentRoot is probably in /etc/apache2/sites-enabled/000-default.conf

- Y



Yehuda -

Thank you.

Found it!

root@meow:/home/ethan# grep -i root  /etc/apache2/sites-enabled/000-default.conf
DocumentRoot /var/www/html

Changed that and it finds the files.

But .

This works perfectly

!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN 
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;

html xmlns=http://www.w3.org/1999/xhtml;
html
head
titleTest Connect2/title
meta http-equiv=Content-Type content=text/html; charset=utf-8 /
style
body{
background-color: #89caeb;
width:100%;
height:100%;
position: relative;
font-family: Helvetica, Arial , Liberation Sans, Free 
sans, sans-serif;
overflow-y: scroll;
}   
/style  

/head
body

strong
div align='center'
  h3Handle Weight/h3
/div
/strong



?php


$hostname=localhost;
$database=Store;
$username=ethan;
$password=;

global $i;


$link = mysqli_connect($hostname, $username, $password);
if (!$link) {
die('Connection failed: ' . mysql_error());
}
else{
 echo Connection to MySQL server  .$hostname .  successful!
 . PHP_EOL;
}

$db_selected = mysqli_select_db($link, $database);
if (!$db_selected) {
die ('Can\'t select database: ' . mysqli_error());
}
else {
echo 'Database ' . $database . ' successfully selected!';
}

?

/body
/html

This fails...It does not even change the background color or print the header

?php
session_name(STORE);
session_set_cookie_params( '24000', '/' );
session_start();
echo 'hello world';
?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN 
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;

html xmlns=http://www.w3.org/1999/xhtml;
html
head
titleHandle Weight/title
meta http-equiv=Content-Type content=text/html; charset=utf-8 /
style
body{
background-color: #89caeb;
width:100%;
height:100%;
position: relative;
font-family: Helvetica, Arial , Liberation Sans, Free 
sans, sans-serif;
overflow-y: scroll;
}   
/style  

/head
body

strong
div align='center'
  h3Handle Weight/h3
/div
/strong
?php
snip

Totally Confused

TIA

Ethan




-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



[users@httpd] Failed to load perl file when restarting Apache 2.2.29 with mod_perl 2.0.8

2015-04-15 Thread Sailaja Gadireddy
Hello Team,


We have installed Apache with mod_perl 2.0.8 and facing the issue when
restarting apache.

Below is the error


*ld.so.1: httpd: fatal: relocation error: file
/opt/pgm/perl/5.10.0/lib/site_perl/5.10.0/sun4-solaris-thread-multi/auto/ARS/ARS.so:
symbol Perl_Istack_sp_ptr: referenced symbol not found*
Please suggest me the way forward to fix the issue.

Thanks  Regards,
Sailaja
IfModule mod_perl.c
  PerlRequire /opt/app/ars/ovsc/perl/startup.pl
PerlModule ModPerl::Registry
PerlModule Apache2::compat
PerlModule Apache2::ServerRec
PerlModule WIH::CaseExchange
Location /wih/caseexchange
AuthTypeBasic
AuthNameCaseExchange
AuthUserFile/opt/web/apache/app/ars/conf/passwd
require valid-user
SetHandler modperl
PerlResponseHandler WIH::CaseExchange
/Location
Location /WIH/CaseExchange
SetHandler modperl
PerlResponseHandler WIH::CaseExchange
/Location
/IfModule

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] httpd 2.4.12 ignoring net.ipv4.ip_local_port_range

2015-04-15 Thread Mike Peachey
Of course you are right. I considered the client would be the issue and do
not now remember why I discounted it. Thank you.

On 14 April 2015 at 17:00, Eric Covener cove...@gmail.com wrote:

 On Tue, Apr 14, 2015 at 6:49 AM, Mike Peachey mike.peac...@port.im
 wrote:
  This client is getting responses from httpd on ports 63156+

 The server side of the connection uses a well-known listening port,
 443.  Clients use those high ephemeral ports.  I don't think tuning an
 ephemeral port range on the server does anything unless you use
 mod_proxy for outbound connections.



 --
 Eric Covener
 cove...@gmail.com

 -
 To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
 For additional commands, e-mail: users-h...@httpd.apache.org




-- 
Mike Peachey
mike.peac...@port.im


Re: [users@httpd] Weird connection issues with mod_proxy_wstunnel

2015-04-15 Thread Yann Ylavic
Hello Marc,

On Wed, Apr 15, 2015 at 10:50 AM, Marc Hörsken i...@marc-hoersken.de wrote:

 Now once a browser has upgraded a connection from HTTP to WebSocket traffic,
 all traffic is proxied to the WebSocket-server at 127.0.0.1:9001. The
 problem is that the browser continues to use that upgraded
 WebSocket-connection for further HTTP-requests, for example to load the next
 page.

 But since all traffic is forwarded to the WebSocket-server, the browser
 receives a 404 from there. So for some reason HTTP- and
 WebSocket-connections are not isolated properly. And Apache2 forwards URLs
 not beginning with /data or /settings.js to the Web-Socket-server.

 Any ideas why this might happen?

Once the connection is upgraded, mod_proxy_wstunnel (as its name
suggests) creates a tunnel between the browser and the application.
It will not check requests boundaries anymore, this is not HTTP but
application data now, and hence application's responsability to not
(make the browser) reuse the same connection for further HTTP
requests.

Regards,
Yann.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



[users@httpd] Weird connection issues with mod_proxy_wstunnel

2015-04-15 Thread Marc Hörsken
Hello everyone,

I am experiencing weird connection issues with mod_proxy_wstunnel. My Apache 2 
web server is still running on Debian Wheezy, so I had to backport 
mod_proxy_wstunnel using the following patches:
https://github.com/mback2k/build-apache2.2-wstunnel

I compiled all mod_proxy* modules using these patches against the apache 2.2.22 
sources provided by apt-get source apache2 on Debian Wheezy.

The following represents the relevant parts of my Apache 2 virtual host 
configuration for https://webgcal.uxnr.de https://webgcal.uxnr.de/

VirtualHost ...:443
ServerName webgcal.uxnr.de
ServerAdmin ...

IfModule mod_ssl.c
...
/IfModule

Alias /media/ /var/local/pyweb/project/webgcal/webgcal/_media/
Alias /static/ /var/local/pyweb/project/webgcal/webgcal/_static/

WSGIDaemonProcess webgcal user=webgcal group=webgcal processes=2 
maximum-requests=100 
python-path=/var/local/pyweb/project/webgcal:/var/local/pyweb/virtualenv/webgcal/lib/python2.7/site-packages
WSGIProcessGroup webgcal
WSGIScriptAlias / /var/local/pyweb/project/webgcal/webgcal/wsgi.py

SetEnv DJANGO_SETTINGS_MODULE ...

Location /data/
ProxyPass ws://127.0.0.1:9001/data/ retry=0 disablereuse=On
ProxyPassReverse ws://127.0.0.1:9001/data/
/Location
Location /settings.js
ProxyPass http://127.0.0.1:9001/settings.js retry=0 
disablereuse=On
ProxyPassReverse http://127.0.0.1:9001/settings.js
/Location
ProxyPreserveHost On
ProxyVia On
/VirtualHost

Now once a browser has upgraded a connection from HTTP to WebSocket traffic, 
all traffic is proxied to the WebSocket-server at 127.0.0.1:9001. The problem 
is that the browser continues to use that upgraded WebSocket-connection for 
further HTTP-requests, for example to load the next page.

But since all traffic is forwarded to the WebSocket-server, the browser 
receives a 404 from there. So for some reason HTTP- and WebSocket-connections 
are not isolated properly. And Apache2 forwards URLs not beginning with /data 
or /settings.js to the Web-Socket-server.

Any ideas why this might happen?

I also tried the original patch to backport mod_proxy_wstunnel available here:
http://blog.cafarelli.fr/2013/04/backporting-apache-support-for-websockets-reverse-proxy-aka-getting-gateone-to-work-behind-apache/
 
http://blog.cafarelli.fr/2013/04/backporting-apache-support-for-websockets-reverse-proxy-aka-getting-gateone-to-work-behind-apache/

I applied the patch using the following approach:
https://i.rationa.li/mark/note/2TWATCchRQGyMA0RlvZSQA 
https://i.rationa.li/mark/note/2TWATCchRQGyMA0RlvZSQA

That approach was also the basis for my own approach that can be found in the 
Github repo mentioned before.

If you want to see the issue in action, you will have to signing to 
webgcal.uxnr.de http://webgcal.uxnr.de/ and create a dummy calendar. This 
will enable the WebSocket-based status functionality of the dashboard.

Thanks in advance.

Best regards,
Marc

Re: [users@httpd] Weird connection issues with mod_proxy_wstunnel

2015-04-15 Thread Marc Hörsken
Hello Yann,

 Am 15.04.2015 um 12:32 schrieb Yann Ylavic ylavic@gmail.com:
 
 Once the connection is upgraded, mod_proxy_wstunnel (as its name
 suggests) creates a tunnel between the browser and the application.
 It will not check requests boundaries anymore, this is not HTTP but
 application data now, …

thanks for the clarification.

 and hence application's responsability to not
 (make the browser) reuse the same connection for further HTTP
 requests.

I was unable to find any useful resources about how to do this, yet.
Can you point me in the right direction?

Is there some special header that needs to be sent by the server?

All examples I found assume that the WebSocket connection is made to a 
different subdomain / host.
But that is not possible for me, because my secure cookies are bound to the 
main domain / host.

I am using SwampDragon [1] with Django and AngularJS.

Thanks in advance.

Best regards,
Marc

 [1] http://swampdragon.net/
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org