On Sunday 06 December 2009, Bob Ionescu wrote:
Am 6. Dezember 2009 14:29 schrieb Michael Renner michael.ren...@gmx.de:
in dem 80er vhost kannst Du das ja dann ausstellen mit ProxyRequests On
Wahrscheinlich muss ich das tun, ja. Nicht sehr elegant. Dewegen mein
Ansatz die Proxynutzung nur
As far as i know apache doesnt support name virtual hosting up to 2.2.13 or
2.2.14 not exactly sure. And after that supports it but only with SII.
On Jan 19, 2010 6:41 PM, Nilesh Govindarajan li...@itech7.com wrote:
On 01/19/2010 12:52 PM, Nasir Zia wrote:
Hi, can anyone tell me can i run
I mean SSL name virtual hosts...
On Jan 19, 2010 7:02 PM, Igor Cicimov icici...@gmail.com wrote:
As far as i know apache doesnt support name virtual hosting up to 2.2.13 or
2.2.14 not exactly sure. And after that supports it but only with SII.
On Jan 19, 2010 6:41 PM, Nilesh Govindarajan
2010/01/19 Nasir Zia
can anyone tell me can i run my two different SSL domains ex:
abc.com and xyz.com on one IP address or i need second IP
address to the server.
Hi Nasir,
what you're looking for is an Apache = 2.2.12 and an
SNI-enabled mod_ssl.
This also imposes restrictions on used
2010/01/19 Edgar Frank
2010/01/19 Nasir Zia
can anyone tell me can i run my two different SSL domains ex:
abc.com and xyz.com on one IP address or i need second IP
address to the server.
what you're looking for is an Apache = 2.2.12 and an
SNI-enabled mod_ssl.
Oh, I meant SNI-enabled
On 01/19/2010 01:32 PM, Igor Cicimov wrote:
As far as i know apache doesnt support name virtual hosting up to 2.2.13
or 2.2.14 not exactly sure. And after that supports it but only with SII.
On Jan 19, 2010 6:41 PM, Nilesh Govindarajan li...@itech7.com
mailto:li...@itech7.com wrote:
On
hello.
2010/1/19 Nilesh Govindarajan li...@itech7.com:
.
Oops. My bad. SSL protocol doesn't give the Host: header. So apache can't
decide which Vhost to serve (from apache docs :D).
..
i think may be apache could if coded little other way, may be more
correctly. i have written about
Hi everyone,
We're experiencing some difficulty that I'm not entirely sure of
the origin of. Most URLs to content in a subdomain link through
the subdomain, but a few are linking a subdirectory of the main
domain instead
domain.ext/subdirectory/content.ext (the few)
subdomain.ext/content.ext
On Tue, Jan 19, 2010 at 2:47 PM, Reese howel...@inkworkswell.com wrote:
Hi everyone,
We're experiencing some difficulty that I'm not entirely sure of
the origin of. Most URLs to content in a subdomain link through
the subdomain, but a few are linking a subdirectory of the main
domain instead
Dear list,
I like to utilize my hosting space with multiple domains. one of these
domain is for typo3 sites. So I have created folders inside
public_html to have individual site. I am using .htaccess to redirect
the domain to its concerned subfolder. There is a folder called TYPO3
inside which
I suggested this:
RewriteEngine On
RewriteRule ^(www\.)?domain\.ext/subdomain/(.*)$ subdomain\.domain\.ext/$2
[R=301,L]
On 19-Jan-10 10:33, Tom Evans wrote:
RewriteRules operate over the part of the URL after the host and
before the query string, so you would be wanting to try out
It looks like that one escaped before I was finished replying.
My apologies.
I suggested this:
RewriteEngine On
RewriteRule ^(www\.)?domain\.ext/subdomain/(.*)$ subdomain\.domain\.ext/$2
[R=301,L]
On 19-Jan-10 10:33, Tom Evans wrote:
RewriteRules operate over the part of the URL after
On 1/19/10, Reese howel...@inkworkswell.com wrote:
RewriteRule ^(www\.)?domain\.ext/subdomain/(.*)$
subdomain\.domain\.ext/$2
RewriteRules operate over the part of the URL after the host and
before the query string, so you would be wanting to try out
RewriteCond.
See
On Jan 16, 2010, at 11:58 AM, Vadkan Jozsef wrote:
what does a self-signed outdated ssl cert worth? [https]
could it be tricked [https] in a way, that the end user will not
recognize? [e.g. he already accepted the cert one time, and the
browser
would warn her, if it been attacked?]
..I
On 19-Jan-10 14:57, Eric Covener wrote:
Tom pointed you to the FAQ that makes your rule appear to be a no-op
and even took the time to restate it in-line.
What, this?
RewriteRules operate over the part of the URL after the host and
before the query string, so you would be wanting to try
Reese wrote:
It tells me that the part after the host (I want to change the host
name) and the part after the query string (that I'm not using if I
understand the usage) are tips of the iceberg. And that is the part
I'm trying to understand. And neither Tom nor you are helping.
Did I not
On 19-Jan-10 15:23, Oliver Schoenborn wrote:
Well, I was going to make an attempt, but with that kind of attitude, doesn't feel right, regardless of how frustratring or voodoo'ish the docs are.
My apologies to you, whether you actually make an attempt or not.
It's frustrating, when you are
On Tue, Jan 19, 2010 at 6:55 AM, Nilesh Govindarajan li...@itech7.comwrote:
Oops. My bad. SSL protocol doesn't give the Host: header. So apache can't
decide which Vhost to serve (from apache docs :D).
Though SSL doesn't itself provide a Host: header, the HTTP session on top if
it still does,
On 19-Jan-10 10:33, Tom Evans wrote:
RewriteRules operate over the part of the URL after the host and
before the query string, so you would be wanting to try out
RewriteCond.
See http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewriterule
, in particular the section labelled 'What is
Have to throw in something here. Tom gave you the right answers. What exactly
is 'one of those'?
The list is comprised of good questions and answers. Not part time employees :)
- Original Message -
From: Reese [howel...@inkworkswell.com]
Sent: 01/19/2010 05:05 PM EST
To:
On 19-Jan-10 17:16, Peter J Milanese wrote:
Have to throw in something here. Tom gave you the right answers. What
exactly is 'one of those'?
RTFM is not always the right answer to the question asked.
The list is comprised of good questions and answers. Not part time
employees :)
My efforts
As stated previously, RewriteRule is NOT the proper directive, and does not see
the hostname.
RewriteCond will act as a filter for the hostname.
RewriteRule will not accomplish what you want, or whatever we 'think' you want.
It does not know anything about hostname.
P
- Original
On Tue, Jan 19, 2010 at 2:42 PM, Peter J Milanese pmilan...@nypl.orgwrote:
As stated previously, RewriteRule is NOT the proper directive, and does not
see the hostname.
RewriteCond will act as a filter for the hostname.
RewriteRule will not accomplish what you want, or whatever we 'think'
On 1/19/10, Jonathan Zuckerman j.zucker...@gmail.com wrote:
I'm pretty sure nobody wants this to turn into a mod_rewrite solve-it-for-me
mailing list.
We only give out the magic incantations on IRC.
--
Eric Covener
cove...@gmail.com
Thanks for your reply.
I don't think the problem is in Router.
Because if I use the other PC with WebServer, all of transactions between
Server and Client is correct.
-Original Message-
From: David Balažic [mailto:xerc...@gmail.com]
Sent: Saturday, January 16, 2010 9:57 PM
To:
25 matches
Mail list logo
