dnesday, April 04, 2007 1:03 PM
> To: General Discussion for the Resin application server
> Subject: Re: [Resin-interest] one resin, one host, but two ports?
>
>
> Scott,
>
> Thanks, again, for giving me a hand.
>
> The setup that includes ${host.regexp[1]} was
Scott,
Thanks, again, for giving me a hand.
The setup that includes ${host.regexp[1]} was something I found while
poking around your documentation. I figure that it is referencing the
expression and giving me the second element. When
I do that in the directive - and include the port - it
didn't
On Apr 2, 2007, at 1:22 PM, Jay Ballinger wrote:
> Scott,
>
> Thanks, very much, for your help. The following does work...
>
>
>
>
>
>
>
> /some/other/path
>
>
>
>
> ...but, is there any way to sneak in a variable in the regexp?
Not in that
Scott,
Thanks, very much, for your help. The following does work...
/some/other/path
...but, is there any way to sneak in a variable in the regexp?
regexp="[^:]+:${someVar}" certainly doesn't work. I've been trying to
find other es
On Apr 2, 2007, at 10:27 AM, Jay Ballinger wrote:
>
>
> My hope would be to use something like the following...
>
>
>
>
>
>
>
>
>
> ...but this results in the 'blank' host directive serving all requests
> - http and https.
Ok, that makes sense.
Hi Scott,
Thanks for the help. Sorry about the confusion, let me try again...
I understand the need for the ... directive. My
challenge is trying to have a universal host name associated with a
port.
For example...
pkcs12
someCerts.p12
On Mar 31, 2007, at 9:41 PM, Jay Ballinger wrote:
> Scott,
>
> I've been playing around with the directives and could use a
> little help.
>
> If I explicitly set the listen ports to 8080 and 8443, and then if I
> set the host names to "foo.bar.com" and "foo.bar.com:8443", it works
> exactly as
Scott,
I've been playing around with the directives and could use a
little help.
If I explicitly set the listen ports to 8080 and 8443, and then if I
set the host names to "foo.bar.com" and "foo.bar.com:8443", it works
exactly as expected by serving pages from different webapp
directories. But I
Thanks, Scott.
I was about to try that combo, but hadn't done it yet. (I have a
laundry list of config items to try.)
I think I remember you giving that same solution to someone a few
weeks ago, now that I think about it. Might be a good candidate for
some examples in the docs. ;)
Thanks again!
On Mar 30, 2007, at 3:33 PM, Jay Ballinger wrote:
> I am setting up a new resin installation and ran into a fork in the
> config.
>
> We would like to have http://foo.bar.com and https://foo.bar.com to be
> answered by the same resin, but with different webapps defined for
> each.
>
> http://fo
I am setting up a new resin installation and ran into a fork in the config.
We would like to have http://foo.bar.com and https://foo.bar.com to be
answered by the same resin, but with different webapps defined for
each.
http://foo.bar.com would answer with a welcome page while ...
https://foo.bar
11 matches
Mail list logo
