Extensive!! Call me on my cell
Eliahu(Elie) Mazin
Network Engineer Security Information
A+, Network+,Security +,MCSE,MCSA,CCENT CCNA,CCNP, CISSP
Imperva , Bluecoat and F5 Expert
781 502 8882 Cell
Office: 781 560 5995
Email: emaz28@xxxxxxxxxxx
-----Original Message-----
From: alin vasile [mailto:alinachegalati@xxxxxxxxx]
Sent: Tuesday, April 20, 2010 7:37 AM
To: users@xxxxxxxxxxxxxxxx
Subject: Re: Re: Apache module that enables ActiveX
what is the activex area in your html?
________________________________
From: Mauri <lain80@xxxxxxxxx>
To: users@xxxxxxxxxxxxxxxx
Sent: Tue, April 20, 2010 1:12:15 PM
Subject: Re: Re: Apache module that enables ActiveX
Hi expert.
I'm sorry for the reply but I'm working for some days with no solution :(
I have this scenario:
SCENARIO 1)
client i.e.7 --> proxy with SSL --> web server in http (I tried https, also)
wireshark output (plain text) in attach: file "with_proxy.txt"
I have apache-2.2.3, mod_proxy and mod_ssl. Below all details.
SCENARIO 2)
client i.e.7 --> web server in http (I tried https, also)
wireshark output (plain text) in attach: file "without_proxy.txt"
In Scenario 2 my browser is running properly the ACTIVEX. In the file in
attach named "GET /reports/TeeFromWeb.asp?teefile=2010420112359_2_teeFile
HTTP/1.1 "
it working fine.
In Scenario 1 the browser don't running properly the activex.
If you see the attach the only difference id correlated to this GET:
"HTTP/1.1 200 OK (GIF89a)" . I suppose that the client interprets the file
as
per an image (GIF).
I don't undestand the reason.
Anyone can help me?
thanks for any suggest.
Cheers,
Mauri
# uname -a
Linux SRV01 2.6.18-128.el5 #1 SMP Wed Dec 17 11:42:39 EST 2008 i686 i686
i386 GNU/Linux
# rpm -qa | grep http
httpd-manual-2.2.3-31.el5_4.2
system-config-httpd-1.3.3.3-1.el5
jakarta-commons-httpclient-3.0-7jpp.1
httpd-2.2.3-31.el5_4.2
httpd-devel-2.2.3-31.el5_4.2
# rpm -qa | grep ssl
openssl-devel-0.9.8e-7.el5
mod_ssl-2.2.3-31.el5_4.2
docbook-style-dsssl-1.79-4.1
openssl-0.9.8e-7.el
2010/4/16 Tom Evans <tevans.uk@googlemail.com>
On Fri, Apr 16, 2010 at 11:43 AM, Mauri <lain80@xxxxxxxxx> wrote:
> in this moment I don't use any others modules. I use mod_proxy and
mod_ssl,
> only.
> Then you mean that the apache mod_proxy don't blocks any activex
request?
> I don't have any problems in this request:
> client --> SERVERA mod_proxy (ex.192.168.0.10) over HTTPS -->
SERVERB web
> server with activex (ex. 192.168.0.11) over HTTP
> If I try to connect to SERVERB the browser read the activex, if I
try to
> connect to SERVERA the browser don't read the activex from the
SERVERB.
> I'll find the problem on SERVERB?
> many thanks for your suggest.
> Cheers,
> Mauri
>
>
So when you go direct to server b it works, and when you go via
server
a it doesn't work? Doesn't sound like anything to do with mod_proxy,
sounds more like the browser refusing to run activex from a
different
security context.
Is the HTML the same?
Do either of the servers report any errors in error_log?
Does the browser?
Have you tried different browsers?
Tom
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server
Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|