New Apigee endpoints to improve SSL »

Today we released a fix for an issue reported by some users in which SSL certificate errors might be seen when accessing an Apigee endpoint. Even though we provide a wildcard certificate for our endpoints, it turns out that SSL is quite conservative in how it handles wildcards and would not permit the subdomain.username.apigee.com pattern without an error.

Now you can address that same endpoint pattern as subdomain-username.apigee.com. All legacy endpoints can be addressed using either pattern, though only the dash pattern will avoid the SSL warnings.

Because we wanted to fix this problem ASAP, we've put it into production before updating the user interface to the new defaults. Give it a try, and do let us know how it works for you. We're also beginning work on SSL for CNAME mapping as a premium feature. If you're interested in being a beta tester, please email .(JavaScript must be enabled to view this email address).