• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 319
  • Last Modified:

How to configure zend ce for subdomain access?

Dear sir,
How to configure zend server ce version(appache) to support web access via following manner:
"http://webmail.xxxx.com   ==  http://www.xxxx.com/webmail/
"
Please give me detail information on how to do this.

Thanks!
0
matiascx
Asked:
matiascx
  • 4
  • 4
1 Solution
 
ahoffmannCommented:
in apache's configuration file use:

RewriteCond %{REQUEST_URI} !^/webmail/
RewriteRule ^$ /webmail/ [L]
0
 
matiascxAuthor Commented:
Sorry, I am a green hand, can you give me more explaination on how to do that and the meaning?

Thanks!
0
 
ahoffmannCommented:
you need to find your apache's configuration file, it's usually named apache.conf or httpd.conf
check if the configuration loads the mod_rewrite module, if not add proper directives to load it
in that file you need to find the proper <directory> directive for the root directory
in that <directory scope you place:
  RewriteEngine On
  RewriteCond %{REQUEST_URI} !^/webmail/
  RewriteRule ^$ /webmail/ [L]

the meaning is that any request which is not /webmail/ (RewriteCond directive) will be rewritten to /webmail (RewriteRule directive)

i.g. this is not the place to explain completely how apache configuration works, there exist dozend of books and million of websites doing it ;-)
0
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

 
matiascxAuthor Commented:
For following description:

the meaning is that any request which is not /webmail/ (RewriteCond directive) will be rewritten to /webmail (RewriteRule directive)

It seems that it is not right? Maybe should be any request which is webmail.xx.xx will be rewritten to xx.xx/webmail

Is my understanding right?
0
 
ahoffmannCommented:
> Maybe should be any request which is webmail.xx.xx
is this what your wish/expect, or what you mean what my rule does?
0
 
matiascxAuthor Commented:
Just because your explaination is not same with my expect or understanding.
I am not sure whether or not it is your mis-writing or my knowledge is error.
Can you clarify the rewrite rule in more detail explaination?
0
 
ahoffmannCommented:
# make a condition for the rewrite:
# check if the URL (which is in the variable %{REQUEST_URI) matches /webmail/ at the beginning (beginning: ^)
# if it does *not* match the condition is true

  RewriteCond %{REQUEST_URI} !^/webmail/

# now, if the condition above was true do the rewrite:
# rewrite an emtpy URL (beginning ^ immediately followed by the end $ ) to /webmail/
# if done, don not continue with rewriterules [L]



  RewriteRule ^$ /webmail/ [L]
0
 
matiascxAuthor Commented:
Thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now