Filed a request:
http://code.google.com/p/googleappengine/issues/detail?id=2753
On Feb 10, 8:59 pm, "Ikai L (Google)" wrote:
> Maybe, as there are other custom protocols we may wish to support on
> Android/Apple App Store/iTunes, etc. Can you file a feature request in our
> issue tracker?
>
> h
Maybe, as there are other custom protocols we may wish to support on
Android/Apple App Store/iTunes, etc. Can you file a feature request in our
issue tracker?
http://code.google.com/p/googleappengine/issues/list
On Wed, Feb 10, 2010 at 1:49 AM, Shai Levy wrote:
> Thanks for the reply!
>
> I act
Thanks for the reply!
I actually already considered what he suggested but had two reason's not to
do so:
1. Security - to me it feels like having a html located on a server which
hold's "trigger" commands to an extension is a risky option and might lead
to code injection vulnerabilities (of course
I actually ended up asking one of the Chrome guys for the answer to this.
This is what he tells me:
"Ah, to me it sounds like GAE's createLoginURL function doesn't recognize
chrome-extension:// as a protocol. It's appending the extension url like a
relative path.
You can tell him to redirect to
I would still appreciate some pointers on this issue.
Is the redirect limited to "http://"; otherwise the API thinks I'm
trying to send to file in my application ? any suggestion how to
overcome this ?
Is there a way to manually create the URL ?
Thanks
On Feb 4, 5:10 pm, Shai wrote:
> Hi,
>
>
