|
|
Recommended: Sing it, brah! 5 fabulous songs for developers
JW's Top 5
Featured White Papers
- Measuring Risk to Improve Java Software Quality
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
Sponsored Links
-
Graph databases are 1000x faster than relational.
Learn More!
-
Career opportunities at Harman- Careers That'll Rock Your Socks Off.
Learn More!
-
Developer-friendly Java PDF libraries by Qoppa Software
Live Demos
-
Stop blaming your app! Diagnose Java performance issues.
Free tool >
-
UrbanCode: Go From Continuous Integration to
Continuous DeliveryLearn More!
Be careful with crossdomain.xml
Submitted by jlward4th on Fri, 02/13/2009 - 11:39.
Back to:
www.javaworld.com/javaworld/jw-02-2009/jw-02-javaee-flex-2.html.
Great article! One comment... For testing it's ok to have a "*" crossdomain.xml policy. But you have to be very careful with those in production. My two general rules of thumb for crossdomain files:
1) NEVER put a "*" policy on a server that uses cookies (especially for authentication)
2) NEVER put a "*" policy on an intranet server
-James
About Us | Advertise | Contact Us | Terms of Service/Privacy | AdChoices
Copyright, 2006-2013 Infoworld, Inc. All rights reserved.