Hi,
My client still uses Netscape 7 on occassion, and I''ve implemented
written the following code to populate a DIV:
new Ajax.Updater(mydiv, ''load_rich_contents'', {
method: ''post'',
parameters: ''myID='' + someVariable,
evalScripts: true
}
This works perfectly in And in Netscape 7, the following appears in
the DIV:
Resource not found
Resource: load_rich_contents POST
For reasons beyond the scope of this question, I''m using POST instead
of GET as I need to ensure that the browser is not cacheing the
results.
Can someone offer a suggestion as to how to make this work in Netscape
7?
Thanks,
Stan McFarland
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
I *think* I''ve solved this problem. According to the docs, Ajax.Updater defaults to post, so the removal of the explicit ''method: ''post'''' line seemed to do the trick. On Feb 4, 10:44 am, Stan McFarland <sfmc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Hi, > > My client still uses Netscape 7 on occassion, and I''ve implemented > written the following code to populate a DIV: > > new Ajax.Updater(mydiv, ''load_rich_contents'', { > method: ''post'', > parameters: ''myID='' + someVariable, > evalScripts: true > > } > > This works perfectly in And in Netscape 7, the following appears in > the DIV: > > Resource not found > Resource: load_rich_contents POST > > For reasons beyond the scope of this question, I''m using POST instead > of GET as I need to ensure that the browser is not cacheing the > results. > > Can someone offer a suggestion as to how to make this work in Netscape > 7? > > Thanks, > > Stan McFarland--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
ok, I misspoke. It turns out the error is not with the GET or POST issue at all, but the fact that my site is an HTTPS site. If I access the site via HTTP, Ajax.Updater works like a champ under Netscape 7. Any suggestions? Thanks, Stan On Feb 5, 10:16 am, Stan McFarland <sfmc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I *think* I''ve solved this problem. According to the docs, > Ajax.Updater defaults to post, so the removal of the explicit ''method: > ''post'''' line seemed to do the trick. > > On Feb 4, 10:44 am, Stan McFarland <sfmc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > Hi, > > > My client still uses Netscape 7 on occassion, and I''ve implemented > > written the following code to populate a DIV: > > > new Ajax.Updater(mydiv, ''load_rich_contents'', { > > method: ''post'', > > parameters: ''myID='' + someVariable, > > evalScripts: true > > > } > > > This works perfectly in And in Netscape 7, the following appears in > > the DIV: > > > Resource not found > > Resource: load_rich_contents POST > > > For reasons beyond the scope of this question, I''m using POST instead > > of GET as I need to ensure that the browser is not cacheing the > > results. > > > Can someone offer a suggestion as to how to make this work in Netscape > > 7? > > > Thanks, > > > Stan McFarland- Hide quoted text - > > - Show quoted text ---~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On Feb 5, 2008 10:02 AM, Stan McFarland <sfmcfar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > ok, I misspoke. It turns out the error is not with the GET or POST > issue at all, but the fact that my site is an HTTPS site.Are you saying that in the address bar the URL is https, and presumably your Ajax request is a relative request to that, right? Like ''/foo/bar'' as opposed to ''http://www.mysite.com/foo/bar''? -justin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---