Thanks a lot Yann!!:)
On Thu, Sep 3, 2015 at 3:51 PM, Yann Ylavic wrote:
> On Thu, Sep 3, 2015 at 11:47 AM, aparna Puram
> wrote:
> > So, This from uri woker properties
> >
> >
> > !/*.png=* works same as ProxyPassMatch \.png$ !
> >
> >
> > ?
&
So, This from uri woker properties
!/*.png=* works same as ProxyPassMatch \.png$ !
?
On Thu, Sep 3, 2015 at 3:15 PM, aparna Puram wrote:
> Sure, Thanks a lot!!:)
>
>
> On Thu, Sep 3, 2015 at 2:08 PM, Yann Ylavic wrote:
>
>> On Thu, Sep 3, 2015 at 10:36 AM,
Sure, Thanks a lot!!:)
On Thu, Sep 3, 2015 at 2:08 PM, Yann Ylavic wrote:
> On Thu, Sep 3, 2015 at 10:36 AM, Yann Ylavic wrote:
> >
> > On Thu, Sep 3, 2015 at 10:13 AM, aparna Puram
> wrote:
> >>
> >> ProxyPass /*.png !
> >
> > ProxyPassMatch
!
ProxyPass /*.htm !
ProxyPassReverse /*.htm !
ProxyPass /*.html !
ProxyPassReverse /*.html !
ProxyPass /*.pdf !
ProxyPassReverse /*.pdf !
--
Regards,
Aparna Puram
+919449473709
k this way?
--
Regards,
Aparna Puram
+919449473709
.
Request you to help me with this.
--
Regards,
Aparna Puram
+919449473709
In httpd.conf file
On 21-Jun-2015 7:37 pm, "Knute Johnson" wrote:
> Got this in my log:
>
> /etc/cron.daily/logrotate:
> apache2: Could not reliably determine the server's fully qualified domain
> name, using 216.240.58.141 for ServerName
>
> Where does apache look for the domain name?
>
> Thanks
In https.conf file
On 21-Jun-2015 7:37 pm, "Knute Johnson" wrote:
> Got this in my log:
>
> /etc/cron.daily/logrotate:
> apache2: Could not reliably determine the server's fully qualified domain
> name, using 216.240.58.141 for ServerName
>
> Where does apache look for the domain name?
>
> Thanks
Hello Team,
Till what limit can the max clients value be increased in linux? is there
any limit in terms of numbers?
and what other parameters are requried to be considered while changing the
max clients values?
--
Regards,
Aparna Puram
+919449473709
ode.*
We have given full access to all the directories in apache on windows.
Still we are getting 500 msg. I am not sure what else am i missing.
--
Regards,
Aparna Puram
+919449473709
bypass this error?
HTTP Web Server: Lotus Notes Exception - Memory allocation request exceeded
65,000 bytes
--
Regards,
Aparna Puram
+919449473709
create any issue as
> I have used both the name in my certificate and also I am not getting any
> error while browsing the website with either name.
> Please correct me if I am wrong or any other pointer that will be helpful.
>
>
>
> Thanks & Regards,
> Bijayant Kumar
>
>
>
>
>
>
--
Regards,
Aparna Puram
+919449473709
change the code to see the
priority column in balancer manager gui.
On Tue, Feb 12, 2013 at 9:02 PM, Jeff Trawick wrote:
> On Tue, Feb 12, 2013 at 6:24 AM, aparna Puram wrote:
>
>> Hello All,
>>
>> Can any one please suggest me on how to enable the priority and
>>
Hi Jim,
We have access logs enabled for the tomcat servers and I used awstats to
measure the no of hits.
On Fri, Feb 8, 2013 at 9:41 PM, Jim Jagielski wrote:
> How are you measuring the load on the backend Tomcats?
>
> On Feb 8, 2013, at 7:57 AM, aparna Puram wrote:
>
>
check if the tomcat is really busy
and that's the reason the apache is not sending request to it.
Are there any tools to measure the load that is being balanced to all the
tomcats?
--
Regards,
Aparna Puram
+919449473709
Check this blog..
http://blog.taddong.com/2011/10/tlssled-v12.html
This might help you to find out if the openssl version that you have
supports the TLSV1.2
On Wed, Jun 13, 2012 at 1:42 AM, Garrison, Jim (ETW)
wrote:
> > -Original Message-
> > From: Eric Covener [mailto:cove...@gmail.co
What is the version of openssl being used?
On Wed, Jun 13, 2012 at 12:29 AM, Garrison, Jim (ETW) wrote:
> The problem appears to be the TLSv1.2 handshake. Here are the cases:
>
>
> * openssl s_client -connect gbit:443
>
> This sends a TLSv1.2 handshake inside a TLSv1.0 CLIENT HELLO, and Apach
Hi,
Sometimes from the huge list of supported cipher suites, It will be hard
for us to select the exact cipher.
If you are working on solaris, You can use the following command to check
the exact cipher and protocol being used by the client.
/opt/csw/bin/openssl s_client -connect clinethostname:
Hello All,
We have implemented the redirects from http to https
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://dnsname.com%{REQUEST_URI}
this server can be accessing using 3 different names.
localhostname
and there are 2dns names for accessing the server.
After implementing
Thanks a lot Mark
I will check with the applicaiton once and come back to you on this.
On Tue, Apr 10, 2012 at 5:56 PM, Mark Montague wrote:
> On April 10, 2012 4:31 , aparna Puram wrote:
>
>> Currently we have only a tomcat installed and all are directly accessing
>> the
Hi,
Did u try rebuilding the apache config file using the following script?
/scripts/rebuildhttpdconf
On Tue, Apr 10, 2012 at 4:38 PM, Luc Saffre wrote:
> Thanks, Eric and Rainer, for your replies.
>
> On 10.04.2012 10:26, Rainer Frey wrote:
> > 2 ideas:
> > * the default site is not enabled
Hello All,
Can we cache webservice calls using Apache.
Currently we have only a tomcat installed and all are directly accessing
the tomcat via apache, And all the webserivice calls are directly being
called from tomcat and this inturn is increasing the load on the tomcat
server.
Is there a way t
regardless of the scheme actually requested. That
> seems to be the behaviour you're asking for.
>
> This all assumes you are using this rule in your port 80 and port 433
> virtualhosts.
>
>
>
> On 18/03/12 17:45, aparna Puram wrote:
> > Hello Spliff,
&g
://
but when I type https:// it is redirecting to https://
I want it to be redirecting to https:// as the ssl certificate CN
: is the dnsname.
On Sun, Mar 18, 2012 at 10:00 AM, SpliFF wrote:
> On 18/03/12 15:02, aparna Puram wrote:
>
> Hello Daniel/Mathijs,
>
> There is only o
type https://selectvcp1.sw.ericsson.se, I m still being in
https://selectvcp1.sw.ericsson.se
I m not sure y. Is there any other way around?
When
On Sun, Mar 18, 2012 at 3:10 AM, Daniel Ruggeri wrote:
> On 3/17/2012 12:58 PM, aparna Puram wrote:
> > Hello All,
> >
> > I am
Hello All,
I am working on a project where I have to redirect all the http requests to
https protocol. I have configured the following rewrite rules and it is
working fine.
RewriteEngine On
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*)$ https://$1 [L,R]
then http:// is redirecting to htt
:
> On 08.12.11 00:38, aparna Puram wrote:
>
>> I understand from your mail that the following 2 cipher suites will work
>> with the existing and the new clinet configurations.
>>
>> Kindly correct me if I m wrong.
>>
>> 1-->!ADH:!EXPORT56:DES-CBC-**SHA
Hello Igor,
Thanks a lot for excellent suggestion...
We will raise this concern to our client. However, There are many third
party servers that are connecting to our webserver, This will take time I
guess.
Hence we will try configuring the following for time being and check if the
new client wit
Hi Igor,
Thanks a zillion.
I understand from your mail that the following 2 cipher suites will work
with the existing and the new clinet configurations.
Kindly correct me if I m wrong.
1-->!ADH:!EXPORT56:DES-CBC-SHA:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
2-->!ADH:!MD5:DES-CBC-SHA:RC4+RSA
Hello ,
Currently we are using the following ciphersuite in our httpd.conf file.
SSLCipherSuite !ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
But our new client does not support the RC4+RSA cipher tag. They support
DES-CBC-SHA tag.
However, There are many other clinets using the
30 matches
Mail list logo