|
What app server are you using? Do you have
any additional security products or servlet filters installed (like
siteminder)? There is a known issue with MSIE and HTTPS
requests that receive responses with no-cache HTTP headers. We try to detect
this situation but you can at least forcibly stop a Flex 2 endpoint from
sending no-cache headers on a response by setting the following in the
secure-amf channel-definition <properties> section: <add-no-cache-headers>false</add-no-cache-headers> Let me know if that fixes the issue. From: I've
setup FDS to build the clients on the server using the secure-amf channel as
the default. The channel uses the java adapter. Now the client that
I'm working on works fine in Firefox. It is able to make calls through
the AMF gateway without any issues. When trying to run the same client in
IE the calls fail to go through. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com YAHOO! GROUPS LINKS
|
- RE: [flexcoders] F2F FDS AMF Issue Peter Farland
- Re: [flexcoders] F2F FDS AMF Issue Joshua Garnett

