I have the follow HTTPService defintion in my mxml page:
Here is my call:
updateRequest.request.value = myvalue;
updateRequest.request.randomNum = Math.random();
The first time call is successful, but second time(after 30
seconds), after send() function call, I didn't even received
HTTPService call from server side. Is this somehow cached or I need
to reinitial it? This looks strange.
I think is browser cache related proxy. I have the same
problem but i haven`t yet tested.
So i think, at the server, you must notify the browser/flash
engine not to cache the result by specifying a header on server
response like "Content-Expires 0" or equivalent. The problem seems
to be only in IE, not in Mozilla. Also, setting useProxy to false
will not work for IE, because of course is false by default and in
your code you haven`t set to true.
Another thought: Event not specified, i supose the prefered
method to pass parameters with httpservice is via send method (
send(parameters) ) because all examples i found on flex docs are
based on simple object wich contain pairs name=> value and wich
is pass as parameter to send method. I don`t know if there are any
significant difference using mx:request or as3 equivalent as in
your example. Maybe it was prefered because is so similar to Ajax
Interesting, in my original message, I used "randomNum" to
make sure each time the request has different randomNum to make
parameters unique. Doesn't that make browser think it is different
URL and won't cache it?
Thanks for the answers, I eventually found out it is the
updateRequest.request.value too long, probably beyond the HTTP GET
limit. That is why my request was never sent out. But surprisingly,
there is no error or warning from Flex. After I use HTTP POST,
everything seems working ok.