empty.html results in 404 over https.

[asingla]

Hi,

I am not shipping the whole system folder under isomorphic directory with my ear file. Now pages with the smartclient components are resulting in 404 errors for the empty.html file. This file is being requested only if application is being accessed over https and not http.

I am not sure what's the purpose of this file but to me the whole helper directory is only for the development environment and should not be shipped for the production env.

Please advise what I should do to avoid this error.

Thanks.

[Isomorphic]

The "helpers" directory must be deployed with your application - it is not development-only (and the docs never suggest this).

[asingla]

Ok.
1) But can you please explain why it happens over https but not http and only for IE? and what's the purpose of this particular file?
2) In general, is there any document which explains the purpose of the files in these directories? this would be very helpful.

Thanks, Amit

[Isomorphic]

1) it's a workaround for a browser bug
2) there's no need for a document, you just need to not decide to delete things at random :)

[asingla]

I agree. Actually Log.html (used for console) file in this directory made me thinking that files in this directory are for development only. And I don't want to expose any file which is not required to increase any security risk. e.g. Log.html might be exposed to say XSS attack and it's really not required in production environment. I think it would be great if you can further split these files so that one knows what should be deployed.

I hope my argument is fair enough.

[Isomorphic]

Log.html should absolutely be deployed in production - it provides critical diagnostics that can be used to troubleshoot problems on a live site (the most important ones to resolve).

[asingla]

That would mean to deploy the "development" directory as well as Log.html depends on that.

[acarur01]

Hi - what did you end up doing about this? I do see that Log.html refers to development directory

<SCRIPT src=../development/ISC_FileLoader.js?isc_version=v8.2p_2012-10-09.js></SCRIPT>
<SCRIPT>isc.FileLoader.modulesDir = "system/development/";</SCRIPT>
<SCRIPT src=../development/ISC_Core.js?isc_version=v8.2p_2012-10-09.js></SCRIPT>
<SCRIPT src=../development/ISC_Foundation.js?isc_version=v8.2p_2012-10-09.js></SCRIPT>
<SCRIPT src=../development/ISC_Containers.js?isc_version=v8.2p_2012-10-09.js></SCRIPT>
<SCRIPT src=../development/ISC_Grids.js?isc_version=v8.2p_2012-10-09.js></SCRIPT>
<SCRIPT src=../development/ISC_Forms.js?isc_version=v8.2p_2012-10-09.js></SCRIPT>
<SCRIPT src=../development/ISC_DataBinding.js?isc_version=v8.2p_2012-10-09.js></SCRIPT>
<SCRIPT src=../development/ISC_Tools.js?isc_version=v8.2p_2012-10-09.js></SCRIPT>

[Isomorphic]

Right - the development directory should be deployed in production environments to support it. This directory basically contains versions of the modules files and should be entirely safe to deploy.

If you have some specific concern / reason for wanting to modify the system directory before deployment, please let us know what your concern is and we can analyze whether there's some real problem that we're unaware of.

Thanks