Thank you very much !!!
Without *addHeader* the following code only worked on IE, but adding this
line also works in Chrome and Firefox.
The problem was Chrome and Firefox html page didn't receive xmlhttp.status
== 200, only xmlhttp.readyState == 4, only received status == 0.
public void doG
Excellent. Thanks very much T.J.. your idea worked.
In my servlet, I overrided the doOptions() method from HttpServlet and
returned the response headers that you suggested:
> response.addHeader("Access-Control-Allow-Origin", "*");
> response.addHeader("Access-Control-Allow-Methods",
> request.g
Hi again,
> I
> _thought_ it was as easy (in this case) as setting the Access-Control-
> Allow-Origin header to * in response to the OPTIONS request, but
> apparently there's more to it as that didn't work in my five-minute
> test, which is all I have time for this morning.
Well, I got to thinkin
Hi,
> T.J, thanks for your reply as well. The answer to your first question
> (the URL of the page that this is part of) is that I'm just having an
> HTML file sitting on my desktop.
AH. That's a very significant piece of information there. :-) Without
it, we're all assuming you're serving the o
Are you sure your servlet is responding with the proper headers. Try
creating a small self-contained minimum test case which fails. Using a
relative URL ensures that it is from the same origin as the loading
page. -Mark
--
You received this message because you are subscribed to the Google Groups
Thanks for the suggestion Scott.
I've tried to add the current timestamp (via the javascript expression
"new Date().getTime()" ) to the parameters and the query string (in
all the combinations such as first adding it only to parameters, then
only to query string, and then to both) and unfortunatel
I have had similar issues before in my applications. I have always
assumes that they were caching issues. With the method as 'post' and
adding the current date and time in the parameters field (or query
string), I've been able to get past this issue.
This is to make sure the url being called is alw
Thanks for correcting me on ActiveX... I didn't know that internally,
an XMLHttpRequest object gets used in the end.
In response to disccomp, I'm not sure how I would use a relative URL.
Could you give an example? I've tried using a value such as /MyApp/
MyServlet, but this doens't work at all (e
Hi,
> From IE, it works just fine
> (probably because it's using ActiveX rather than XMLHttpRequest)
Not *rather than* -- it's using XMLHttpRequest regardless. On older
versions of IE, the way you get one is via ActiveX, but that's
irrelevant (and only older versions); it's an XMLHttpRequest
rega
Try using a relative URL, and prototype does not call activeX.
--
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptacul...@googlegroups.com.
To unsubscribe from this group, send ema
Thanks for the quick reply.. yes, I have tried clearing the cache in
both firefox and chrome, but still no luck.
--Ronen
On Mar 13, 4:14 am, Guillaume Lepicard
wrote:
> hi ronen,
> could it be a browser cache issue ? have you tried clearing cache before
> running ajax ?
>
> On Fri, Mar 12, 2010
11 matches
Mail list logo
