subdomain

I am trying to create a subdomain using the Zend Router, and then for each section under a subdomain, such as subdomain.site.com/section/ I am creating another route and then trying to chain it to the subdomain route. but I don't know how. I have read all the documentation I could find and all the forums, but it leads me to figure it out on my own. So far, my attempts just get me this error: Catchable fatal error: Argument 2 passed to Zend_Controller_Router_Rewrite::addRoute() must implement interface Zend_Controller_Router_Route_Interface, null given, called in /var/local/zend/library/Zend

While I realise that this is usually related to cross site scripting attacks, what I'm wondering is how can a session remain valid throughout multiple subdomains belonging to a single domain (example: a user logging in only once, and being able to access both subdomain1.domain.com and subdomain2.domain.com with the same session). I guess I first need to understand how it works, but so far I haven't been able to find much that would be of any relevance. But then again, maybe I wasn't asking the right question. Thanks in advance :) Inproc sessions cannot remain valid, however you can code your

I have a wildcard SSL from Godaddy. When I go here: https://conciergelive.conciergeliveapp.com/users_session/new Everything is fine. But when I go here: https://es.conciergelive.conciergeliveapp.com/users_session/new I get a security alert. I need the extra subdomain to determine locality. Any ideas why this does not work? According to RFC 2818 Http Over SSL, section 3.1: Names may contain the wildcard character * which is considered to match any single domain name component or component fragment. E.g., *.a.com matches foo.a.com but not bar.foo.a.com it explains why the name *.conciergeliveapp

This has probably been asked but I can't find a straight answer, or the ones I found don't work. I have one domain mydomain.com , resolving to an IP; let's call it 8.8.8.8. The DNS settings also point two subdomains to that IP address with an A record. These are dev.mydomain.com and staging.mydomain.com . Both have an A-record pointing to 8.8.8.8. On the server (8.8.8.8) I have two virtual hosts files. These are as follows: staging.mydomain.com.conf <VirtualHost *:80> ServerName staging.mydomain.com DocumentRoot /var/www/html/mydomain.com/staging/ </VirtualHost> And... dev.mydomain.com.conf

Here is my scenario: I have an application that will have to support multiple clients. Each client will be given a subdomain for there service. We will also have a brochure website that doesn't have the application, its just a website about the product and how potential clients can setup an account with us. Given: www.mycoolsite.com would point to a brochure app on Heroku. client1.mycoolsite.com , client2.mycoolsite.com and client3.mycoolsite.com would all point to the same SaaS application that could tell the difference between each request and I should be able to handle so they only see

The idea is to take incoming requests to http://abc.example.com/... and rewrite them to http://example.com/abc/... That's easy enough to do with a 301/302 redirect: # rewrite via 301 Moved Permanently server { listen 80; server_name abc.example.com; rewrite ^ $scheme://example.com/abc$request_uri permanent; } The trick is to do this URL change transparently to the client when abc.example.com and example.com point at the same Nginx instance. Put differently, can Nginx serve the contents from example.com/abc/... when abc.example.com/... is requested and without another client round trip ?