wildcard-subdomain

I know there have been a few threads on this before, but I have tried absolutely everything suggested (that I could find) and nothing has worked for me thus far... With that in mind, here is what I'm trying to do: First, I want to allow users to publish pages and give them each a subdomain of their choice (ex: user.mysite.com). From what I can gather, the best way to do this is to map user.mysite.com to mysite.com/user with mod_rewrite and .htaccess - is that correct? If that is correct, can somebody give me explicit instructions on how to do this? Also, I am doing all of my development

I'm using HttpClient on Android to connect to https://someUrl.com/somePath . The problem is that the site's certificate is for *.someUrl.com, not someUrl.com, so I get an SSLException. Lame on the part of the site, yes, but unless I can get it fixed, I'm stuck. Is there a way I can get HttpClient to relax and accept the certificate? noah This is my (edited) solution: class MyVerifier extends AbstractVerifier { private final X509HostnameVerifier delegate; public MyVerifier(final X509HostnameVerifier delegate) { this.delegate = delegate; } @Override public void verify(String host, String[] cns,

Is anyone aware of a public wildcard domain name that resolves to IP address 127.0.0.1. For example if I wanted to test a URL locally such as mywebsite.localhost.com or example.localhost.com but I don't have control of DNS settings (hosts file or whatever) then I would use this public DNS to resolve to 127.0.0.1. It needs to be wildcarded so that no matter whatever comes before localhost.com it still resolves to 127.0.0.1. *.vcap.me VMWare maintains this for their open cloud platform . 37Signals created a complete domain for mapping to any IP you want, http://xip.io . So for localhost you can

When I go to https://wild.rileylark.appspot.com with chrome, I get the nice "this is going great " icon. When I use firefox 4, I get the "omg, you're effed " message: wild.rileylark.appspot.com uses an invalid security certificate. The certificate is only valid for the following names: *.appspot.com , *.*.appspot.com , appspot.com Is this normal? Anything I can do to fix this? So the specific condition here is that the name on the certificate is *.appspot.com , and *.*.appspot.com appears within the cert's Subject Alternate Names field. A rejected Chrome bug covers this exact scenario . In it,

I'm going to be using flask to create a web application, and part of the application will involve a subdomain (for example, user1.appname.org). I'm not sure how to go about creating these subdomains dynamically in the flask configuration, or how to deploy them to a production server. What is the best way of doing this? All Flask's routing constructs support the subdomain keyword argument (this includes support for route variables). @app.route("/", subdomain="static") def static_index(): """Flask supports static subdomains This is available at static.your-domain.tld""" return "static.your

we have wildcard ssl certificate for *.domain.com, and have a website with sub1.sub2.domain.com safari 4.0.4 on MacOsx pops up a certificate error(presumably because of wildcard interpretation), while safari 4 on windows does not. also ie8 behaviour is mixed at best, some ie8 do not display the certificate error and some do not. What causes this strange behavior on Safari and IE? A wildcard SSL certificate for *.example.net will match sub.example.net but not sub.sub.example.net . From RFC 2818 : Matching is performed using the matching rules specified by RFC2459 . If more than one identity of