[google-appengine] Re: https support
We have implemented an interim solution for one of our clients and would like to learn if there is broader interest for us to productize it. http://earlystageit.wordpress.com/2009/09/17/secure-access-to-google-app-engine/ Any and all suggestions welcome. On Aug 22, 1:03 am, repairman alau2...@gmail.com wrote: google guys, I don't know if you guys realize the implication of not getting a static IP? if I have a domain (abc.com) I cannot map it to the appspot subdomain without an IP and I have to resort to a redirect. And search engines are not friendly to redirects. And no serious website will ever want to redirect to blah.appsot.com it just looks unprofessional. So this lack of static IP is preventing google app engine from becoming actually useful like EC2 for real business. And that's why there is no serious apps or serious ecommerce systems running on your GAE so far despite of all the hype. It's almost like selling a car without headlights i.e. sounds like a small miss but it will prevent the car you are selling from being popular. no serious person can drive only during the day time. Please don't think of this static IP problem from the techie point of view, think from your 'customers' perspective. This is a show stopper! GAE is such a good concept and can revolutionize the industry but this lack of static IP is such a spoiler! On Aug 6, 7:27 am, Tony fatd...@gmail.com wrote: Fair enough. I'm fine with we're working on solutions, as long as it's not sorry, wait for the world to upgrade to FF3/IE8. On Aug 6, 10:21 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi Tony, We're looking into solutions. It's not as simple as it may first appear - in the case of a service like Amazon EC2, your server resides at only a single physical location, and so does theIPaddress you rent. In contrast, App Engine apps are served from IPs at Google datacenters around the globe. -Nick Johnson On Thu, Aug 6, 2009 at 3:18 PM, Tonyfatd...@gmail.com wrote: Why not charge a monthly fee for apps to get astaticIP(like Amazon does)? Scarcity of supply seems like a bit of a cop-out to me - it's not apparent that a majority of app engine apps require thissupport. The customers you're losing because of this, however, are customers that plan to process e-commerce transactions online without looking like a phishing scam. Customers that make money on your service are more likely to spend money on your service. On Aug 5, 3:55 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi J Singh, Due to the way SSL works, this is not currently possible without allocating anIPaddress for each App Engine domain that would use SSL - which itself isn't very practical due to IPv4 address scarcity. The latest version of SSL supports using a singleIPaddress for multiple sites with different certificates, but browsersupportfor this version is not yet nearly widespread enough to make it a practical alternative. -Nick Johnson On Wed, Aug 5, 2009 at 5:39 AM, J Singhj.si...@earlystageit.com wrote: For an appengine-based site,https://abc.appspot.comiscurrentlysupported buthttps://www.abc.comcannotbesupported. I know there is a technical hurdle to cross but didn't know if any techniques had been proposed for being able to usewww.abc.comwithSSLconnections? Thanks. J Singh Managing Director Early Stage IT (978) 760-2055 http://www.earlystageit.com -- Nick Johnson, Developer Programs Engineer, App Engine -- Nick Johnson, Developer Programs Engineer, App Engine --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support
I have an idea, throwing it out to this group to see if it is sound. What if there were a service in the cloud that served as an https proxy? https://www.abc.com would resolve to this service and its sole job would be to be a proxy for https://abc.appspot.com. Well, there is the performance problem of the extra hop, and the trust problem of whether we trust this service to not look at messages as it terminates the SSL certs at either end. Are there any other problems that anyone can see? It might be a nice short-term solution until Google comes up with their solution. Amazon's $0.01/hr translates to $7.20 per month. What if this service were priced similarly? How many folks would buy it? Does such a service already exist? On Aug 24, 6:44 am, Kris Walker kixxa...@gmail.com wrote: repairman, I'm building what I hope will be a real business on GAE. In particular, my system design is not possible in environments like EC2, because of the extra configuration and overhead involved in holding a static IP. That was a design decision by Amazon. Not having a static IP was a design decision by Google, and it offers a different set of advantages. If there were only a few different kinds of things on the planet that we could eat, we would have no chefs. When creating a great dining experience for your customers you need a variety of ingredients to put together that 5 star dish. My hat is off to the GAE team for carefully considering their design implications. I hope they continue to keep their ear to the crowd, but hold their ground to offer the ingredients we need to make great products, rather than just anything that everyone else has. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support
On Tue, Aug 25, 2009 at 12:53 PM, J j.si...@earlystageit.com wrote: I have an idea, throwing it out to this group to see if it is sound. What if there were a service in the cloud that served as an https proxy? https://www.abc.com would resolve to this service and its sole job would be to be a proxy for https://abc.appspot.com. Well, there is the performance problem of the extra hop, and the trust problem of whether we trust this service to not look at messages as it terminates the SSL certs at either end. Said service would have to have a unique IP per domain it proxies. This could be difficult to scale given the relative scarcity of IPv4 addresses these days. As you point out, it would also require routing all requests via a single location. Are there any other problems that anyone can see? It might be a nice short-term solution until Google comes up with their solution. Amazon's $0.01/hr translates to $7.20 per month. What if this service were priced similarly? How many folks would buy it? Does such a service already exist? I believe Amazon's EC2 instances start at $0.10 per hour, not $0.01. You could serve many domains with one machine, potentially, but I'm not sure if Amazon will let you associate multiple elastic IPs with the same EC2 instance. -Nick Johnson On Aug 24, 6:44 am, Kris Walker kixxa...@gmail.com wrote: repairman, I'm building what I hope will be a real business on GAE. In particular, my system design is not possible in environments like EC2, because of the extra configuration and overhead involved in holding a static IP. That was a design decision by Amazon. Not having a static IP was a design decision by Google, and it offers a different set of advantages. If there were only a few different kinds of things on the planet that we could eat, we would have no chefs. When creating a great dining experience for your customers you need a variety of ingredients to put together that 5 star dish. My hat is off to the GAE team for carefully considering their design implications. I hope they continue to keep their ear to the crowd, but hold their ground to offer the ingredients we need to make great products, rather than just anything that everyone else has. -- Nick Johnson, Developer Programs Engineer, App Engine --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support
On Aug 25, 3:27 pm, Nick Johnson (Google) nick.john...@google.com wrote: I believe Amazon's EC2 instances start at $0.10 per hour, not $0.01. You could serve many domains with one machine, potentially, but I'm not sure if Amazon will let you associate multiple elastic IPs with the same EC2 instance. That's correct. A better option would be Rackspace - they offer cloud servers for $0.015/hour, which is about $11/month. Bandwidth is billed separately per GB, just like Amazon EC2. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support
Sorry, I was referring to the $0.01/hr that Amazon charges for reserving an IP address, thinking that a the proxy server was essentially serving the same function. On Aug 25, 8:27 am, Nick Johnson (Google) nick.john...@google.com wrote: On Tue, Aug 25, 2009 at 12:53 PM, J j.si...@earlystageit.com wrote: I have an idea, throwing it out to this group to see if it is sound. What if there were a service in the cloud that served as an https proxy?https://www.abc.comwould resolve to this service and its sole job would be to be a proxy forhttps://abc.appspot.com. Well, there is the performance problem of the extra hop, and the trust problem of whether we trust this service to not look at messages as it terminates the SSL certs at either end. Said service would have to have a unique IP per domain it proxies. This could be difficult to scale given the relative scarcity of IPv4 addresses these days. As you point out, it would also require routing all requests via a single location. Are there any other problems that anyone can see? It might be a nice short-term solution until Google comes up with their solution. Amazon's $0.01/hr translates to $7.20 per month. What if this service were priced similarly? How many folks would buy it? Does such a service already exist? I believe Amazon's EC2 instances start at $0.10 per hour, not $0.01. You could serve many domains with one machine, potentially, but I'm not sure if Amazon will let you associate multiple elastic IPs with the same EC2 instance. -Nick Johnson On Aug 24, 6:44 am, Kris Walker kixxa...@gmail.com wrote: repairman, I'm building what I hope will be a real business on GAE. In particular, my system design is not possible in environments like EC2, because of the extra configuration and overhead involved in holding a static IP. That was a design decision by Amazon. Not having a static IP was a design decision by Google, and it offers a different set of advantages. If there were only a few different kinds of things on the planet that we could eat, we would have no chefs. When creating a great dining experience for your customers you need a variety of ingredients to put together that 5 star dish. My hat is off to the GAE team for carefully considering their design implications. I hope they continue to keep their ear to the crowd, but hold their ground to offer the ingredients we need to make great products, rather than just anything that everyone else has. -- Nick Johnson, Developer Programs Engineer, App Engine --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support
Hi repairman, Redirects are not required in order to serve traffic from your own domain. You can simply set up Google Apps on your domain (for free), and use that to map a subdomain (for example, www.abc.com) to your App Engine app. Naked domains (abc.com) are not currently supported, but that will not impact your search engine rankings if you ensure your authoritative domain is the qualified (www.abc.com) one and people link to that. You can use your registrar's redirect service to send requests for abc.com/* to www.abc.com/*for manually entered links. http://code.google.com/appengine/articles/domains.html -Nick Johnson On Sat, Aug 22, 2009 at 6:03 AM, repairman alau2...@gmail.com wrote: google guys, I don't know if you guys realize the implication of not getting a static IP? if I have a domain (abc.com) I cannot map it to the appspot subdomain without an IP and I have to resort to a redirect. And search engines are not friendly to redirects. And no serious website will ever want to redirect to blah.appsot.com it just looks unprofessional. So this lack of static IP is preventing google app engine from becoming actually useful like EC2 for real business. And that's why there is no serious apps or serious ecommerce systems running on your GAE so far despite of all the hype.It's almost like selling a car without headlights i.e. sounds like a small miss but it will prevent the car you are selling from being popular. no serious person can drive only during the day time. Please don't think of this static IP problem from the techie point of view, think from your 'customers' perspective. This is a show stopper!GAE is such a good concept and can revolutionize the industry but this lack of static IP is such a spoiler! On Aug 6, 7:27 am, Tony fatd...@gmail.com wrote: Fair enough. I'm fine with we're working on solutions, as long as it's not sorry, wait for the world to upgrade to FF3/IE8. On Aug 6, 10:21 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi Tony, We're looking into solutions. It's not as simple as it may first appear - in the case of a service like Amazon EC2, your server resides at only a single physical location, and so does theIPaddress you rent. In contrast, App Engine apps are served from IPs at Google datacenters around the globe. -Nick Johnson On Thu, Aug 6, 2009 at 3:18 PM, Tonyfatd...@gmail.com wrote: Why not charge a monthly fee for apps to get astaticIP(like Amazon does)? Scarcity of supply seems like a bit of a cop-out to me - it's not apparent that a majority of app engine apps require this support. The customers you're losing because of this, however, are customers that plan to process e-commerce transactions online without looking like a phishing scam. Customers that make money on your service are more likely to spend money on your service. On Aug 5, 3:55 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi J Singh, Due to the way SSL works, this is not currently possible without allocating anIPaddress for each App Engine domain that would use SSL - which itself isn't very practical due to IPv4 address scarcity. The latest version of SSL supports using a singleIPaddress for multiple sites with different certificates, but browser support for this version is not yet nearly widespread enough to make it a practical alternative. -Nick Johnson On Wed, Aug 5, 2009 at 5:39 AM, J Singhj.si...@earlystageit.com wrote: For an appengine-based site, https://abc.appspot.comiscurrentlysupported buthttps://www.abc.comcannotbe supported. I know there is a technical hurdle to cross but didn't know if any techniques had been proposed for being able to usewww.abc.comwithSSLconnections? Thanks. J Singh Managing Director Early Stage IT (978) 760-2055 http://www.earlystageit.com -- Nick Johnson, Developer Programs Engineer, App Engine -- Nick Johnson, Developer Programs Engineer, App Engine -- Nick Johnson, Developer Programs Engineer, App Engine --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support
repairman, I'm building what I hope will be a real business on GAE. In particular, my system design is not possible in environments like EC2, because of the extra configuration and overhead involved in holding a static IP. That was a design decision by Amazon. Not having a static IP was a design decision by Google, and it offers a different set of advantages. If there were only a few different kinds of things on the planet that we could eat, we would have no chefs. When creating a great dining experience for your customers you need a variety of ingredients to put together that 5 star dish. My hat is off to the GAE team for carefully considering their design implications. I hope they continue to keep their ear to the crowd, but hold their ground to offer the ingredients we need to make great products, rather than just anything that everyone else has. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support
Star it, bro: http://code.google.com/p/googleappengine/issues/detail?id=792colspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary%20Log%20Component On Fri, Aug 21, 2009 at 10:03 PM, repairmanalau2...@gmail.com wrote: google guys, I don't know if you guys realize the implication of not getting a static IP? if I have a domain (abc.com) I cannot map it to the appspot subdomain without an IP and I have to resort to a redirect. And search engines are not friendly to redirects. And no serious website will ever want to redirect to blah.appsot.com it just looks unprofessional. So this lack of static IP is preventing google app engine from becoming actually useful like EC2 for real business. And that's why there is no serious apps or serious ecommerce systems running on your GAE so far despite of all the hype. It's almost like selling a car without headlights i.e. sounds like a small miss but it will prevent the car you are selling from being popular. no serious person can drive only during the day time. Please don't think of this static IP problem from the techie point of view, think from your 'customers' perspective. This is a show stopper! GAE is such a good concept and can revolutionize the industry but this lack of static IP is such a spoiler! On Aug 6, 7:27 am, Tony fatd...@gmail.com wrote: Fair enough. I'm fine with we're working on solutions, as long as it's not sorry, wait for the world to upgrade to FF3/IE8. On Aug 6, 10:21 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi Tony, We're looking into solutions. It's not as simple as it may first appear - in the case of a service like Amazon EC2, your server resides at only a single physical location, and so does theIPaddress you rent. In contrast, App Engine apps are served from IPs at Google datacenters around the globe. -Nick Johnson On Thu, Aug 6, 2009 at 3:18 PM, Tonyfatd...@gmail.com wrote: Why not charge a monthly fee for apps to get astaticIP(like Amazon does)? Scarcity of supply seems like a bit of a cop-out to me - it's not apparent that a majority of app engine apps require this support. The customers you're losing because of this, however, are customers that plan to process e-commerce transactions online without looking like a phishing scam. Customers that make money on your service are more likely to spend money on your service. On Aug 5, 3:55 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi J Singh, Due to the way SSL works, this is not currently possible without allocating anIPaddress for each App Engine domain that would use SSL - which itself isn't very practical due to IPv4 address scarcity. The latest version of SSL supports using a singleIPaddress for multiple sites with different certificates, but browser support for this version is not yet nearly widespread enough to make it a practical alternative. -Nick Johnson On Wed, Aug 5, 2009 at 5:39 AM, J Singhj.si...@earlystageit.com wrote: For an appengine-based site,https://abc.appspot.comiscurrentlysupported buthttps://www.abc.comcannotbe supported. I know there is a technical hurdle to cross but didn't know if any techniques had been proposed for being able to usewww.abc.comwithSSLconnections? Thanks. J Singh Managing Director Early Stage IT (978) 760-2055 http://www.earlystageit.com -- Nick Johnson, Developer Programs Engineer, App Engine -- Nick Johnson, Developer Programs Engineer, App Engine --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support
google guys, I don't know if you guys realize the implication of not getting a static IP? if I have a domain (abc.com) I cannot map it to the appspot subdomain without an IP and I have to resort to a redirect. And search engines are not friendly to redirects. And no serious website will ever want to redirect to blah.appsot.com it just looks unprofessional. So this lack of static IP is preventing google app engine from becoming actually useful like EC2 for real business. And that's why there is no serious apps or serious ecommerce systems running on your GAE so far despite of all the hype.It's almost like selling a car without headlights i.e. sounds like a small miss but it will prevent the car you are selling from being popular. no serious person can drive only during the day time. Please don't think of this static IP problem from the techie point of view, think from your 'customers' perspective. This is a show stopper!GAE is such a good concept and can revolutionize the industry but this lack of static IP is such a spoiler! On Aug 6, 7:27 am, Tony fatd...@gmail.com wrote: Fair enough. I'm fine with we're working on solutions, as long as it's not sorry, wait for the world to upgrade to FF3/IE8. On Aug 6, 10:21 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi Tony, We're looking into solutions. It's not as simple as it may first appear - in the case of a service like Amazon EC2, your server resides at only a single physical location, and so does theIPaddress you rent. In contrast, App Engine apps are served from IPs at Google datacenters around the globe. -Nick Johnson On Thu, Aug 6, 2009 at 3:18 PM, Tonyfatd...@gmail.com wrote: Why not charge a monthly fee for apps to get astaticIP(like Amazon does)? Scarcity of supply seems like a bit of a cop-out to me - it's not apparent that a majority of app engine apps require this support. The customers you're losing because of this, however, are customers that plan to process e-commerce transactions online without looking like a phishing scam. Customers that make money on your service are more likely to spend money on your service. On Aug 5, 3:55 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi J Singh, Due to the way SSL works, this is not currently possible without allocating anIPaddress for each App Engine domain that would use SSL - which itself isn't very practical due to IPv4 address scarcity. The latest version of SSL supports using a singleIPaddress for multiple sites with different certificates, but browser support for this version is not yet nearly widespread enough to make it a practical alternative. -Nick Johnson On Wed, Aug 5, 2009 at 5:39 AM, J Singhj.si...@earlystageit.com wrote: For an appengine-based site,https://abc.appspot.comiscurrentlysupported buthttps://www.abc.comcannotbe supported. I know there is a technical hurdle to cross but didn't know if any techniques had been proposed for being able to usewww.abc.comwithSSLconnections? Thanks. J Singh Managing Director Early Stage IT (978) 760-2055 http://www.earlystageit.com -- Nick Johnson, Developer Programs Engineer, App Engine -- Nick Johnson, Developer Programs Engineer, App Engine --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support
Why not charge a monthly fee for apps to get a static IP (like Amazon does)? Scarcity of supply seems like a bit of a cop-out to me - it's not apparent that a majority of app engine apps require this support. The customers you're losing because of this, however, are customers that plan to process e-commerce transactions online without looking like a phishing scam. Customers that make money on your service are more likely to spend money on your service. On Aug 5, 3:55 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi J Singh, Due to the way SSL works, this is not currently possible without allocating an IP address for each App Engine domain that would use SSL - which itself isn't very practical due to IPv4 address scarcity. The latest version of SSL supports using a single IP address for multiple sites with different certificates, but browser support for this version is not yet nearly widespread enough to make it a practical alternative. -Nick Johnson On Wed, Aug 5, 2009 at 5:39 AM, J Singhj.si...@earlystageit.com wrote: For an appengine-based site,https://abc.appspot.comis currently supported buthttps://www.abc.comcan not be supported. I know there is a technical hurdle to cross but didn't know if any techniques had been proposed for being able to usewww.abc.comwith SSL connections? Thanks. J Singh Managing Director Early Stage IT (978) 760-2055 http://www.earlystageit.com -- Nick Johnson, Developer Programs Engineer, App Engine --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support
Hi Tony, We're looking into solutions. It's not as simple as it may first appear - in the case of a service like Amazon EC2, your server resides at only a single physical location, and so does the IP address you rent. In contrast, App Engine apps are served from IPs at Google datacenters around the globe. -Nick Johnson On Thu, Aug 6, 2009 at 3:18 PM, Tonyfatd...@gmail.com wrote: Why not charge a monthly fee for apps to get a static IP (like Amazon does)? Scarcity of supply seems like a bit of a cop-out to me - it's not apparent that a majority of app engine apps require this support. The customers you're losing because of this, however, are customers that plan to process e-commerce transactions online without looking like a phishing scam. Customers that make money on your service are more likely to spend money on your service. On Aug 5, 3:55 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi J Singh, Due to the way SSL works, this is not currently possible without allocating an IP address for each App Engine domain that would use SSL - which itself isn't very practical due to IPv4 address scarcity. The latest version of SSL supports using a single IP address for multiple sites with different certificates, but browser support for this version is not yet nearly widespread enough to make it a practical alternative. -Nick Johnson On Wed, Aug 5, 2009 at 5:39 AM, J Singhj.si...@earlystageit.com wrote: For an appengine-based site,https://abc.appspot.comis currently supported buthttps://www.abc.comcan not be supported. I know there is a technical hurdle to cross but didn't know if any techniques had been proposed for being able to usewww.abc.comwith SSL connections? Thanks. J Singh Managing Director Early Stage IT (978) 760-2055 http://www.earlystageit.com -- Nick Johnson, Developer Programs Engineer, App Engine -- Nick Johnson, Developer Programs Engineer, App Engine --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support
Fair enough. I'm fine with we're working on solutions, as long as it's not sorry, wait for the world to upgrade to FF3/IE8. On Aug 6, 10:21 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi Tony, We're looking into solutions. It's not as simple as it may first appear - in the case of a service like Amazon EC2, your server resides at only a single physical location, and so does the IP address you rent. In contrast, App Engine apps are served from IPs at Google datacenters around the globe. -Nick Johnson On Thu, Aug 6, 2009 at 3:18 PM, Tonyfatd...@gmail.com wrote: Why not charge a monthly fee for apps to get a static IP (like Amazon does)? Scarcity of supply seems like a bit of a cop-out to me - it's not apparent that a majority of app engine apps require this support. The customers you're losing because of this, however, are customers that plan to process e-commerce transactions online without looking like a phishing scam. Customers that make money on your service are more likely to spend money on your service. On Aug 5, 3:55 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi J Singh, Due to the way SSL works, this is not currently possible without allocating an IP address for each App Engine domain that would use SSL - which itself isn't very practical due to IPv4 address scarcity. The latest version of SSL supports using a single IP address for multiple sites with different certificates, but browser support for this version is not yet nearly widespread enough to make it a practical alternative. -Nick Johnson On Wed, Aug 5, 2009 at 5:39 AM, J Singhj.si...@earlystageit.com wrote: For an appengine-based site,https://abc.appspot.comiscurrently supported buthttps://www.abc.comcannot be supported. I know there is a technical hurdle to cross but didn't know if any techniques had been proposed for being able to usewww.abc.comwithSSL connections? Thanks. J Singh Managing Director Early Stage IT (978) 760-2055 http://www.earlystageit.com -- Nick Johnson, Developer Programs Engineer, App Engine -- Nick Johnson, Developer Programs Engineer, App Engine --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support
Hi J Singh, Due to the way SSL works, this is not currently possible without allocating an IP address for each App Engine domain that would use SSL - which itself isn't very practical due to IPv4 address scarcity. The latest version of SSL supports using a single IP address for multiple sites with different certificates, but browser support for this version is not yet nearly widespread enough to make it a practical alternative. -Nick Johnson On Wed, Aug 5, 2009 at 5:39 AM, J Singhj.si...@earlystageit.com wrote: For an appengine-based site, https://abc.appspot.com is currently supported but https://www.abc.com can not be supported. I know there is a technical hurdle to cross but didn't know if any techniques had been proposed for being able to use www.abc.com with SSL connections? Thanks. J Singh Managing Director Early Stage IT (978) 760-2055 http://www.earlystageit.com -- Nick Johnson, Developer Programs Engineer, App Engine --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: https support for dev_appserver.py?
Hi Jeff, Great suggestion. I looked in the issue tracker and it looks like someone posted and issue for this and several share this need. Please star it since you are interested :-) http://code.google.com/p/googleappengine/issues/detail?id=960 Cheers, Jeff On Sun, Jul 19, 2009 at 12:19 AM, Jeff Enderwick jeff.enderw...@gmail.comwrote: Looks like dev_appserver.py doesn't support http (secure in app.yaml). Any thoughts about adding that? Or did I miss something? Thanks! Jeff --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: HTTPS Support for appspot.com
Really great news. On Oct 20, 2:47 pm, Filip [EMAIL PROTECTED] wrote: Thanks for this! Looking forward to SNI on arbitrary domain names, but this will solve the problem for now, and it makes a really big difference. Filip. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: HTTPS Support for appspot.com
You must have the 1.1.5 version of the SDK to use the 'secure' argument in
your app.yaml.
-Marzia
On Fri, Oct 17, 2008 at 8:52 PM, fssfans [EMAIL PROTECTED] wrote:
???
what's going on?
Console
Unexpected attribute 'secure' for object of type class
'google.appengine.api.ap
pinfo.URLMap'.
my app.yaml
-
application: fssmain
version: 1
runtime: python
api_version: 1
handlers:
- url: /account/.*
script: main.py
login: required
secure: always
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---
[google-appengine] Re: HTTPS Support for appspot.com
Thanks for this! Looking forward to SNI on arbitrary domain names, but this will solve the problem for now, and it makes a really big difference. Filip. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: HTTPS Support for appspot.com
I wonder if another workaround for the IP-based limitations of SSL is to dynamically assign a port for SSL for each app. So, I've got www.myapp.com and when my app is started up, you assign www.myapp.com:7520 for SSL. Another app on the server might get 7521, etc. The assignment is only while the app is running. If the app is killed off that server, the port is freed up for another app. So, as long as you have a larger block of potential IP addresses than the number of apps running simultaneously on a server, you should be fine (and there should be plenty of available ports). One disadvantage of this is that the special port will require a special redirect, but I think that's manageable. On Oct 16, 3:03 pm, Marzia Niccolai [EMAIL PROTECTED] wrote: You may be wondering why we're only supporting appspot.com right now, and not arbitrary Google Apps domains. This has to do with fundamental limitations in the SSL protocol (see:http://en.wikipedia.org/wiki/Https#Limitations). We're currently investigating workarounds for this using e.g. http://en.wikipedia.org/wiki/Server_Name_IndicationSNI (http://en.wikipedia.org/wiki/Server_Name_Indication), which provides a viable solution for newer browsers--we'll keep you posted! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: HTTPS Support for appspot.com
I wonder if another workaround for the IP-based limitations of SSL is to dynamically assign a port for SSL for each app Oh, and you could potentially support Server Name Indication for newer clients and dynamic ports for older clients. A big advantage of all of us running on GAE is that you can deal with the hassle once and all the apps can take advantage of it. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: HTTPS Support for appspot.com
??? what's going on? Console Unexpected attribute 'secure' for object of type class 'google.appengine.api.ap pinfo.URLMap'. my app.yaml - application: fssmain version: 1 runtime: python api_version: 1 handlers: - url: /account/.* script: main.py login: required secure: always --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: HTTPS Support for appspot.com
HTTPS support is really great. Here is a summary of remaining security issues with App Engine. * Support HTTPS for arbitrary domains (not just *.appspot.com) This request is being tracked in issue 792: http://code.google.com/p/googleappengine/issues/detail?id=792 * urlfetch doesn't verify HTTPS certificates See issue 46 http://code.google.com/p/googleappengine/issues/detail?id=46, which is now (for some reason beyond my understanding) a duplicate of issue 61: http://code.google.com/p/googleappengine/issues/detail?id=61 * Mail API should support TLS See issue 497: http://code.google.com/p/googleappengine/issues/detail?id=497 * Uploading the app to App Engine servers over HTTPS See issue 794: http://code.google.com/p/googleappengine/issues/detail?id=794 * Secure access to the Admin Console (appengine.google.com) See issue 795: http://code.google.com/p/googleappengine/issues/detail?id=795 Feel free to add to this list. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: HTTPS Support for appspot.com
Hi Alexander, Good point about 46 being marked a duplicate of 44. I've de-duped it. Cheers, Jeff On Oct 17, 10:41 am, Alexander Konovalenko [EMAIL PROTECTED] wrote: HTTPS support is really great. Here is a summary of remaining security issues with App Engine. * Support HTTPS for arbitrary domains (not just *.appspot.com) This request is being tracked in issue 792:http://code.google.com/p/googleappengine/issues/detail?id=792 * urlfetch doesn't verify HTTPS certificates See issue 46http://code.google.com/p/googleappengine/issues/detail?id=46, which is now (for some reason beyond my understanding) a duplicate of issue 61:http://code.google.com/p/googleappengine/issues/detail?id=61 * Mail API should support TLS See issue 497:http://code.google.com/p/googleappengine/issues/detail?id=497 * Uploading the app to App Engine servers over HTTPS See issue 794:http://code.google.com/p/googleappengine/issues/detail?id=794 * Secure access to the Admin Console (appengine.google.com) See issue 795:http://code.google.com/p/googleappengine/issues/detail?id=795 Feel free to add to this list. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: HTTPS Support for appspot.com
well done On Fri, Oct 17, 2008 at 6:03 AM, Marzia Niccolai [EMAIL PROTECTED] wrote: One of the most frequently requested features for App Engine has been HTTPS serving capabilities. Today we're excited to announce that App Engine now supports incoming HTTPS connections using a certificate valid for all appspot.com URLs. Here's how it works: * app.yaml files now support a new handler attribute, called secure: - url: /accounts/.* script: admin.py login: admin *secure: always* *This attribute can be either always, optional, or never (default), and determines the behavior of the handler for HTTP and HTTPS requests. See our documentation for more details: http://code.google.com/appengine/docs/configuringanapp.html#Secure_URLs * HTTPS requests have their own bandwidth quotas, but also count toward your total bandwidth quotas. You can monitor these quotas on your dashboard. You may be wondering why we're only supporting appspot.com right now, and not arbitrary Google Apps domains. This has to do with fundamental limitations in the SSL protocol (see: http://en.wikipedia.org/wiki/Https#Limitations). We're currently investigating workarounds for this using e.g. http://en.wikipedia.org/wiki/Server_Name_IndicationSNI ( http://en.wikipedia.org/wiki/Server_Name_Indication), which provides a viable solution for newer browsers--we'll keep you posted! This functionality is already available starting with the 1.1.5 SDK. -- Stay hungry,Stay foolish. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: HTTPS Support for appspot.com
Hi Google Hmm, this is EXCELLENT progress! Than you for listenting. Might I suggest that you also offer a few custom whitelabel domains, like securecheckout.com, secureconnection.net or something? Main domain is not as necessary as it looking professional. /mattias On 17 Okt, 02:31, kang [EMAIL PROTECTED] wrote: well done On Fri, Oct 17, 2008 at 6:03 AM, Marzia Niccolai [EMAIL PROTECTED] wrote: One of the most frequently requested features for App Engine has been HTTPS serving capabilities. Today we're excited to announce that App Engine now supports incoming HTTPS connections using a certificate valid for all appspot.com URLs. Here's how it works: * app.yaml files now support a new handler attribute, called secure: - url: /accounts/.* script: admin.py login: admin *secure: always* *This attribute can be either always, optional, or never (default), and determines the behavior of the handler for HTTP and HTTPS requests. See our documentation for more details: http://code.google.com/appengine/docs/configuringanapp.html#Secure_URLs * HTTPS requests have their own bandwidth quotas, but also count toward your total bandwidth quotas. You can monitor these quotas on your dashboard. You may be wondering why we're only supporting appspot.com right now, and not arbitrary Google Apps domains. This has to do with fundamental limitations in the SSL protocol (see: http://en.wikipedia.org/wiki/Https#Limitations). We're currently investigating workarounds for this using e.g. http://en.wikipedia.org/wiki/Server_Name_IndicationSNI ( http://en.wikipedia.org/wiki/Server_Name_Indication), which provides a viable solution for newer browsers--we'll keep you posted! This functionality is already available starting with the 1.1.5 SDK. -- Stay hungry,Stay foolish. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
