Hi there,
I have just a one question to prototype''s Ajax.Request calls and hope
that someone could answer it.
Ajax.Requests via a http to a https is not possible, even if it''s the
same domain. Is that right?
For example:
your login form is here - http://www.mydomain.com
the call points to: https://www.mydomain.com/library/login.php
i.e.
var url = ''https://www.mydomain.com/library/login.php'';
var params = $(''loginForm'').serialize(true);
var myAjax = new Ajax.Request (url, {
method: ''post'',
parameters: params,
onComplete: function(req) {
yada yada yada...
},
.
.
.
});
Is there any way to make this work?
Thanks a lot for any answer,
Michael
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
Hi, That''s indeed a violation of SOP (http://en.wikipedia.org/wiki/ Same_origin_policy). The easiest work-around would be to use https://www.mydomain.com for your login form. Best, Tobie On Apr 1, 4:48 pm, Jarkand <supp...-4/aaYhHQNL7QT0dZR+AlfA@public.gmane.org> wrote:> Hi there, > > I have just a one question to prototype''s Ajax.Request calls and hope > that someone could answer it. > > Ajax.Requests via a http to a https is not possible, even if it''s the > same domain. Is that right? > > For example: > your login form is here -http://www.mydomain.com > the call points to:https://www.mydomain.com/library/login.php > > i.e. > var url = ''https://www.mydomain.com/library/login.php''; > var params = $(''loginForm'').serialize(true); > var myAjax = new Ajax.Request (url, { > method: ''post'', > parameters: params, > onComplete: function(req) { > yada yada yada... > }, > . > . > . > > }); > > Is there any way to make this work? > > Thanks a lot for any answer, > Michael--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Hi and thanks for the info! Well, and that''s actually the "uncool" thing about it. Having a page with a "log in" link that opens a floating window incl. the log in form makes SSL calls not possible. However, thanks for the quick reply. Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
> Having a page with a "log in" link that opens a floating window incl. > the log in form makes SSL calls not possible.I think Tobie''s point was that if the page itself is served via https, it solves the problem. So rather than having an http-served page with a login link, you''d have an https-served page with a login link. It can even be the same page and be smart, in that it sees it was served via http and if you click the login link, loads itself (in the normal way) via https and then presents the login floater; but if it sess it was served with https, it just shows the floater without the reload. -- T.J. Crowder tj / crowder software / com On Apr 1, 5:24 pm, Jarkand <supp...-4/aaYhHQNL7QT0dZR+AlfA@public.gmane.org> wrote:> Hi and thanks for the info! > > Well, and that''s actually the "uncool" thing about it. > > Having a page with a "log in" link that opens a floating window incl. > the log in form makes SSL calls not possible. > > However, thanks for the quick reply. > Michael--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---