Re: [Resin-interest] SSL - Different cert per virtual host?
it can be done also with one IP but using different ports. It is inpossible to use Name Virtual hosts on same socket (this is a https limit not a resin or apache limit) Riccardo Cohen wrote: yes but it can't be the same IP. your serveur must have several IP, one for each certificate. Mattias Jiderhamn wrote: Hi, I want to know if it is possible to set up Resin to use multiple SSL certificates on the same server, each used for a different (virtual) host? That is, I want the same Resin instance to correspond both to foo.com with its SSL certificate and bar.com with its SSL certificate (on the same port). Is that possible? How? /Mattias ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] configuring webdav
both with and without the trailing slash give 404 responses. /webdav/ was not found on this server. Resin-3.0.19 (built Mon, 15 May 2006 04:50:47 PDT) the logs do show the webdav servlet starting, but give no error on the 404; only msg.log shows [11:13:30.936] webdav: init and access.log says only GET /webdav/ HTTP/1.1 404 and that got me thinking: I wonder if it disallows LIST commands? Sure enough, when I put a file into my webdav dir and tried /webdav/test.xml, I get the file. so my updated question is: how do I enable directory listing? I tried simply taking out the trailing slash in /webdav/* but it gave the same behaviour as before. On Thu, Sep 25, 2008 at 4:19 PM, Knut Forkalsrud [EMAIL PROTECTED] wrote: PS: It would be nice if Resin's WebDAV servlet implemented the LOCK operation such that MacOSX would mount a WebDAV server as a read/write file system. ah and that might be my show-stopper right there, because that was more or less exactly what I needed to do :( ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Velocity rendering dies
On Sep 25, 2008, at 10:12 PM, tweihs wrote:
Folks,
I've apparently found a way to kill the Velocity parsing in resin
3.1.3 and
3.1.4 (pro). We use velocity style syntax extensively throughout
the our
site and this hurdle is baffling me. I can confirm via a simple
velocityEnabled.jsp that if I comment out most of our app's
web.xml and
leave in the jsp velocity-enabled=true tag, I can print
variables out
with velocity syntax. If I uncomment the remaining tags in web.xml
(I'll
refer to this as web.xml.dev), velocity dies.
Can you check this on 3.2.0? We did disable velocity on some of the
earlier 3.1 releases (due to internal refactoring of JSP parsing.)
-- Scott
I downloaded our web.xml (I'll refer to this as web.xml.prod )
file from
production and velocity works again. Thus, there is something being
loaded
(a resource, jms queue, resin db, one of our classes) via the web.xml.dev
that neuters velocity. I'm trying to comment blocks out to see what
resource is the offender, but due to the size of our web.xml file,
this will
take a bit more toggling to get to the source. I'll continue doing
that to
isolate, but curious if there is anything that could end up
disabling the
velocity rendering. The *parsing* works - that is, the pages get
compiled.
It's just that blocks like ${foo} don't get rendered. Things that
come to
mind:
* something with logging? I noticed some errors about Log4J not
being able
to write to a directory due to perms, and curious if logging somehow
dies,
does velocity rendering die?
* jar file issues? I've noticed including or excluding some jars,
like
struts (and jakarta commons logging and log4j), can also neuter the
rendering. This would seem less likely to be the culprit in this
case,
because downloading web.xml.prod and running with that re-enables
velocity.
Thanks in advance,
-tyson
--
View this message in context:
http://www.nabble.com/Velocity-rendering-dies-tp19682616p19682616.html
Sent from the Resin mailing list archive at Nabble.com.
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] configuring webdav
On Sep 25, 2008, at 1:19 PM, Knut Forkalsrud wrote: On Sep 23, 2008, at 7:23 AM, Gary Lawrence Murphy wrote: servlet-mapping url-pattern='/webdav/*' servlet-name='webdav'/ ... but when I use a browser to access localhost:8080/webdav I get a 404 Not-Found error. ... what did I miss? It could be as simple as adding a trailing slash in your URL, after all there is an explicit slash in the servlet mapping. -Knut PS: It would be nice if Resin's WebDAV servlet implemented the LOCK operation such that MacOSX would mount a WebDAV server as a read/ write file system. Right. That's the main open issue with Resin's WebDAV. -- Scott ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Comet param via hessian
OK, that did not work!!! To recap: I am trying to pass some value to hessian comet from action script.(ex: member id string room name). Since from .as you can't pass a param to the hessian comet servlet (I wonder why?) and there is no BAM example for action script(and I do not know if BAM works on port 80) Emil recommended: Try this: Create a bean that shared between the comet servlet and a Hessian POJO/servlet within the same web-app. Passing data via application scope works as Emil said... but there's no way to ID what user that is, so that the right users info is passed. (the examples register socket to action script, but no way to ID the user)(if I put it in the app context ... what if another request comes, I have not unique id, not sure how to tell in hessian coment what user that data goes w/). Ex: Using the regular hessian to pass some data via user's uniqe session w/ .as I do: ServletRequest request = ServiceContext.getContextRequest(); HttpServletRequest req = (HttpServletRequest) request; HttpSession ses = req.getSession(true); and put data in ses. Then comet Hessian I do this: HttpServletRequest req = (HttpServletRequest) request; HttpSession ses = req.getSession(false); to get the data. It tells me the session is not there, but I did call the 1st servlet already. My requirement is to register a user to a room and be able to push. Again, if I can pass data to comet for .as, good, which I can't. Or if I can make a a user session in regular hessian, and access that user session in comet hessian. Or something else. tia. .V ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Comet param via hessian
OK, that did not work!!! To recap: I am trying to pass some value to hessian comet from action script.(ex: member id string room name). Since from .as you can't pass a param to the hessian comet servlet (I wonder why?) and there is no BAM example for action script(and I do not know if BAM works on port 80) Emil recommended: Try this: Create a bean that shared between the comet servlet and a Hessian POJO/servlet within the same web-app. Passing data via application scope works as Emil said... but there's no way to ID what user that is, so that the right users info is passed. (the examples register socket to action script, but no way to ID the user)(if I put it in the app context ... what if another request comes, I have not unique id, not sure how to tell in hessian coment what user that data goes w/). Ex: Using the regular hessian to pass some data via user's uniqe session w/ .as I do: ServletRequest request = ServiceContext.getContextRequest(); HttpServletRequest req = (HttpServletRequest) request; HttpSession ses = req.getSession(true); and put data in ses. Then comet Hessian I do this: HttpServletRequest req = (HttpServletRequest) request; HttpSession ses = req.getSession(false); to get the data. It tells me the session is not there, but I did call the 1st servlet already. My requirement is to register a user to a room and be able to push. Again, if I can pass data to comet for .as, good, which I can't. Or if I can make a a user session in regular hessian, and access that user session in comet hessian. Or something else. tia. .V ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] SSL - Different cert per virtual host?
You may try to use multiple host names in a single cert. Tested with apache only, not with resin. Anyway, all vhosts have to use the same cert. Maybe some of the following notes can help: - csr generation tool using subjectAltName extension wget http://svn.cacert.org/CAcert/CSRGenerator/csr - csr generation by script (will add subjectAltName extension to conf) sh csr - modifying opennssl.cnf in order to sign request with extension [ v3_ca ] subjectAltName = critical,DNS:localhost1,DNS:localhost2 - signing the cert request openssl x509 -req -days 99 -extfile /etc/ssl/openssl.cnf \ -extensions v3_ca -in lxwww2_csr.pem \ -signkey host_privatekey.pem -out host_crt.pem - check csr and crt (must contain X509v3 Subject Alternative Name) openssl req -in host_csr.pem -noout -text openssl x509 -in host_crt.pem -noout -text - security issuses with subjectAltName and esp. wildcards: http://nils.toedtmann.net/pub/subjectAltName.txt - browser compability http://wiki.cacert.org/wiki/VhostTaskForce#InteroperabilityTest and http://www.switch.ch/pki/meetings/2007-01/namebased_ssl_virtualhosts.pdf Best regards Martin -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Mattias Jiderhamn Gesendet: Montag, 29. September 2008 12:24 An: Resin Betreff: [Resin-interest] SSL - Different cert per virtual host? Hi, I want to know if it is possible to set up Resin to use multiple SSL certificates on the same server, each used for a different (virtual) host? That is, I want the same Resin instance to correspond both to foo.com with its SSL certificate and bar.com with its SSL certificate (on the same port). Is that possible? How? /Mattias ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
