113 reputation
5
bio website
location Virginia
age 32
visits member for 5 years, 2 months
seen Nov 25 '09 at 21:22

I'm a Senior Software Developer at Liberty University in Lynchburg, VA. I'm married and have three sons. I primarily work on mobile solutions in iOS, Android, and mobile web.


Dec
15
awarded  Popular Question
Apr
22
awarded  Student
Nov
25
awarded  Scholar
Nov
25
comment CNAME causing “Server Not Found” with AWS S3
Just to clarify why I chose this as the answer: Amazon S3 apparently takes a while to setup a bucket for viewing.
Nov
25
accepted CNAME causing “Server Not Found” with AWS S3
Nov
25
comment CNAME causing “Server Not Found” with AWS S3
This works for me: static.imdoingscience.com.s3.amazonaws.com/images/head.png This was not: static.imdoingscience.com/images/head.png I did just check it again though, and it's suddenly working. Aren't CNAME entries supposed to be instantaneous? Why should it take 18 hours for it to start working? Does Amazon need a certain amount of time after the creation of a bucket for the webservice to begin working with it?
Nov
25
awarded  Editor
Nov
25
revised CNAME causing “Server Not Found” with AWS S3
Formatting
Nov
25
asked CNAME causing “Server Not Found” with AWS S3
Aug
25
awarded  Autobiographer