Oops, sorry if I double-posted -- I thought my original post bounced due to
a missing subject.
Interesting, thanks Scott.
Aaron
-Original Message-
From: resin-interest-boun...@caucho.com
[mailto:resin-interest-boun...@caucho.com] On Behalf Of Scott Ferguson
Sent: Friday, February 06, 200
On Feb 6, 2009, at 1:21 PM, Aaron Freeman wrote:
> Under Resin-3.0.x the following code works whether I pass in a
> 'email' param
> or not. However on Resin 3.2.1, which I just installed .. It throws
> an
> exception if an 'email' param wasn't passed in. However it works
> great if I
> do
Under Resin-3.0.x the following code works whether I pass in a 'email' param
or not. However on Resin 3.2.1, which I just installed .. It throws an
exception if an 'email' param wasn't passed in. However it works great if I
do pass an email param in. Any thoughts?
The work around
Under Resin-3.0.x the following code works _whether I pass in a 'email'
param or not_. However on Resin 3.2.1, which I just installed .. It throws
an exception if an 'email' param wasn't passed in. However it works great if
I do pass an email param in. Any thoughts?
Thanks,
Aaron
On Feb 6, 2009, at 6:05 AM, Ronan Lucio wrote:
> inds a httpd process consuming 200% from CPU
>
> It got the application much more stable, but once in a while (once in
> week for example) I have the same problem: server gets almost
> unresponsive.
> So as a workaround it run a "killall -1 httpd
>
> On Feb 6, 2009, at 9:22 AM, BUSCH Steffen wrote:
>
> >
> > Thanks Scott, I think I'm aware of 80 % of the passwords and can
> > regenerate them.
> > As I'm having several external passwords files with the old base64
> > encoded passwords for different web-apps, it would be great if you
> >
On Feb 6, 2009, at 9:22 AM, BUSCH Steffen wrote:
>
> Thanks Scott, I think I'm aware of 80 % of the passwords and can
> regenerate them.
> As I'm having several external passwords files with the old base64
> encoded passwords for different web-apps, it would be great if you
> could
> advise how
>
> On Feb 6, 2009, at 8:15 AM, BUSCH Steffen wrote:
>
> > Hi all,
> >
> > I have a small Issue while trying to prepare the upgrade from Resin
> > 2.1.14 to Resin 3.1 Snapshot as of 19th December with the Digest
> > Password in Resin XmlAuthenticator.
>
> 2.1.14 had an incorrect implementation
On Feb 6, 2009, at 8:15 AM, BUSCH Steffen wrote:
> Hi all,
>
> I have a small Issue while trying to prepare the upgrade from Resin
> 2.1.14 to Resin 3.1 Snapshot as of 19th December with the Digest
> Password in Resin XmlAuthenticator.
2.1.14 had an incorrect implementation of base64 encoding.
Hi all,
I have a small Issue while trying to prepare the upgrade from Resin
2.1.14 to Resin 3.1 Snapshot as of 19th December with the Digest
Password in Resin XmlAuthenticator.
I used to have the following configuration in Resin 2.1.14
com.caucho.http.security.XmlAuthenticator
Hi,
I have a server with apache+resin-3.1.6 installed.
Once in a while it have some performance issues. I have noted on that times:
- theres is one (or two) httpd process consuming 200% (each process)
from CPU
- after some time (few hours) application gets almost unresponsive (most
of request h
Hi,
Is there a way to limit access to "/caucho-status" URL either per
IP or per user/password?
I read that it's suggested to disable it in production servers, but it
has good information for monitoring servers.
I think it would be nice to just limit accesses.
Ronan
__
12 matches
Mail list logo
