Close
Glad You're Ready. Let's Get Started!

Let us know how we can contact you.

Thank you!

We'll respond shortly.

PIVOTAL LABS
Standup 9/27/2010: Careful with S3 wildcard certs and bucketnames

Ask for Help

“Does anybody have solutions for a public sandbox?”

They want people to be able to modify their data, but want the data to roll itself back to the clean state at specific times, or after certain events have happened.

Some people are having problems with the latest RubyMine EAP build. When using our standard keyboard map they are unable to make new lines, they have to use Shift-Enter.

Interesting Things

  • People have good things to say about http://html5boilerplate.com/
  • A team ran into a problem with https and S3. Using the bucketname.s3.amazonaws.com syntax instead of the s3.amazonaws.com/bucketname syntax can fail when using https if your bucketname has too many segments. This is a known limitation of wildcard certificates.

Comments
  1. Mike Grafton says:

    Re: the S3/HTTPS thing: to elaborate, the problem you’ll encounter is that browsers (and other clients) will think your certificate is invalid. So don’t name you bucket

    my.bucketname.here

    …if you are combining the S3 “virtual hosting” URL style with HTTPS.

    Mike

Post a Comment

Your Information (Name required. Email address will not be displayed with comment.)

* Copy This Password *

* Type Or Paste Password Here *