Sorry, logging in after a while. Hopefully you have solved the problem by now. Answering just in case some one stumbles upon through Google.
The problem is not the proxy, it is that you are accessing SITE B (localhost:*8080*) from SITE A (localhost:*8000*) from within the browser, which is disallowed by default and can be permitted by setting appropriate HTTP Headers. (SO Answer<http://stackoverflow.com/questions/1653308/access-control-allow-origin-multiple-origin-domains> ). Alternatively you can have SITE A "play" reverse proxy<http://en.wikipedia.org/wiki/Reverse_proxy>for SITE B. On 28 March 2014 11:46, rmu <sendmail4...@gmail.com> wrote: > Hi, I have been stuck in the same *proxy* thing. While I tried to get wfs > point layer from geoserver in openlayers i got error in the chrome console: > > 1. OPTIONS http://localhost:8080/geoserver/EMIS/wfs No > 'Access-Control-Allow-Origin' header is present on the requested resource. > Origin 'http://localhost:8000' is therefore not allowed access. > > OpenLayers.js:1188<http://localhost:8000/site_media/Openlayers/OpenLayers.js> > > XMLHttpRequest cannot load http://localhost:8080/geoserver/EMIS/wfs. No > 'Access-Control-Allow-Origin' header is present on the requested resource. > Origin 'http://localhost:8000 <http://localhost/>' is therefore not > allowed access. > I believe you have solved it using GeoNodes Proxy. I am just starting > django and Geodjango. I have few questions: > 1. Is the Proxy an app of the GeoNode? > a. Can I copy the Proxy folder inside by project directory and include > it in installed apps of the settings.py file. > 2. Would you guide me to use the proxy/view.py. How did you use it? > > please help me!! > Sincerely, > Ram Shrestha > > On Saturday, February 1, 2014 9:17:27 PM UTC+5:45, Gkpetrak wrote: >> >> Hi Me Sulphur, >> >> Thank you so much my friend ! >> A two weeks problem solved !! >> The problem was the csrfmiddleware token in my POST request. >> >> Thank you in advance, >> George >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-users/u57bbBirVuY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/f246303b-4eca-4e59-a9b7-3bcc90f6814f%40googlegroups.com<https://groups.google.com/d/msgid/django-users/f246303b-4eca-4e59-a9b7-3bcc90f6814f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CABSvzZD%3DLuqfEo_vHmBdg8b2HfT3DGOsRs5AXv-VpRZ_J3kz4w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
