Hi,
I have this well-known issue with Access-Control-Allow-Origin in my Spring application. I use cross-domain request to read data from built in MongoDB database REST interface (for example : http:\localhost:28017\db_name\collection_name).
My javascript client (JSONP doesnt work :( ) is very similar to this one on this webpage : http://2rdscreenretargeting.blogspot...or-jersey.html. I also use CORS Filter from this website : http://software.dzhuvinov.com/cors-filter.html.
Every response from my Spring app has in their header this Access-Control-Allow-Origin attribute, except response from mongodb. What else can i do ?
I also found that mongod has parameter --json which Permits JSONP access via an HTTP interface. Consider the security implications of allowing this activity before enabling this option, but even enabling this option does not change anything i suppose ;/
Best regards,
Lucas
I have this well-known issue with Access-Control-Allow-Origin in my Spring application. I use cross-domain request to read data from built in MongoDB database REST interface (for example : http:\localhost:28017\db_name\collection_name).
My javascript client (JSONP doesnt work :( ) is very similar to this one on this webpage : http://2rdscreenretargeting.blogspot...or-jersey.html. I also use CORS Filter from this website : http://software.dzhuvinov.com/cors-filter.html.
Every response from my Spring app has in their header this Access-Control-Allow-Origin attribute, except response from mongodb. What else can i do ?
I also found that mongod has parameter --json which Permits JSONP access via an HTTP interface. Consider the security implications of allowing this activity before enabling this option, but even enabling this option does not change anything i suppose ;/
Best regards,
Lucas