Hey All, I know there have been many<https://groups.google.com/forum/?fromgroups#!topic/Google-Web-Toolkit/PAaDf7a_5zI> CDN<https://groups.google.com/forum/?fromgroups#!searchin/google-web-toolkit/cdn/google-web-toolkit/kuyQU4y0RTo/vDLANu9os2kJ> related<https://groups.google.com/forum/?fromgroups#!searchin/google-web-toolkit/cdn/google-web-toolkit/IHf6BPFUWWw/MU5Yh0vdWSAJ>questions here before, but I found no answers for this problem.
So here are the constraints: - Serve all RPC calls and index.html from EC2 site (i.e. www.site.com) - Serve everything else from CloudFront CDN (i.e. static.site.com) - Use GWTP with code splitting (so no XS Linker) - Use SSL for thinks like login So, if you do this, you'll get the "Blocked a frame with origin " http://static.site.com"; from accessing a frame with origin " http://www.site.com <http://localhost/>". Protocols, domains, and ports must match" To my knowledge CORS does not help with this. CORS is for XHR requests, not frames. Sadly I cannot just put index.html on the CDN and use passthrough for RPC's with CORS because CDN entries should be uniquely names, otherwise you must invalidate them and this will cause inconsistencies during deployment untli all 34 edge nodes eventually sync up (15min to 2 hours). Additionally, named SSL was just supported on Wednesday<http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html> at a cost of $600/mo, otherwise the site can only be served from a very ugly CF URL. That's is too pricey for most anyone. So, is there anyway to serve all the static files from a CDN with the index.html on another domain without using the XS linker (to retain code splitting)? Thanks for your wisdom. I've been scraping scripts together to get this whole deployment automated and will put it all into a GWT on AWS post when we're finally deployed. Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
