It's not clear from your message if you login again before accessing your https URLs or if you just change the protocol part of the URL from http to https (i.e. adding a "s") or do you login again before hitting your URL using https?
The cookie you'll receive for http isn't valid for your https URLs, so you need to login again. Andi On Tue, Jul 13, 2010 at 7:18 PM, john <john.tur...@gmail.com> wrote: > I have a handler with the "secure: optional" setting in my app.yaml > file. When I make http requests to one of its url's, the data is > retrieved and returned no problem. When I make an https to the same > url, however, the handler's call to users.get_current_user() returns > None, so that the request cannot be processed (and my code returns > 401). > > Has anyone had this problem with https requests? I presume the user- > cookie-info isn't getting included in the appropriate request header, > but I have no idea why that might be or how to fix it. If anyone can > help with this, I would sure appreciate 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-appeng...@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. > > -- 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-appeng...@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.
