Hi Jerome,
You can get around that with a proxy server. Google for "openlayers proxy"
and hopefully you should find something.
Basically you can't do XML stuff unless the browser sees it going to and
coming from the same domain/port as the application. so
www.example.com/webapp. You're using a different port, which is normal.
Thus the conventional solution is to set up a simple proxy script.
Regards,
Jonathan
On 6 November 2013 14:56, Jerome A. Wendell <[email protected]>wrote:
> Jonathan,
>
>
>
> I installed the MapFish printing servlet as you suggested, and can print
> OSM and WMS layers fine using a GET request. I have been trying to print
> vector layers, and the spec information for the print request exceeds the
> maximum length of a GET request. I have been trying to use POST, but I get
> the following error:
>
>
>
> XMLHttpRequest cannot load
> http://www.mydomain.com:8080/print/pdf/create.json. Origin
> http://www.mydomain.com is not allowed by Access-Control-Allow-Origin.
>
>
>
> I have researched this error, and found a possible solution to be at the
> following link:
>
>
>
> http://enable-cors.org/index.html
>
>
>
> I have checked and the suggested information to put into the web.config
> file on IIS7 is already in the web.config on our server. I also found some
> information for a cross origin filter for Jetty at the following link:
>
>
>
>
> http://stackoverflow.com/questions/8303162/jetty-cross-origin-filter/8454168#8454168
>
>
>
> I have tried adding that to the web.xml file for MapFish print, and it
> doesn’t appear to have any affect. I added it to the web.xml file for
> GeoServer, and it seems to break a number of things.
>
>
>
> Have you or anyone else experienced the Access-Control-Allow-Origin
> problem, and what did you do to fix it? Any suggestions?
>
>
>
> Thanks,
>
>
>
> Jerome
>
>
>
> *From:* Jonathan Moules [mailto:[email protected]]
> *Sent:* Thursday, October 31, 2013 8:35 AM
> *To:* [email protected]
> *Cc:* Jesse Eichar; Mauro Bartolomeoli; GeoServer Mailing List List
> *Subject:* Re: [Geoserver-users] GeoServer Printing Module
>
>
>
> Hi Jerome,
>
> You're already using Jetty - it's the server that Geoserver runs out of.
> Stick it in the webapps directory and it should work. You'll need to
> restart jetty/geoserver of course.
>
>
>
> Jonathan
>
>
>
>
>
> On 31 October 2013 12:31, Jerome A. Wendell <[email protected]>
> wrote:
>
> Jonathan,
>
>
>
> Thanks for your reply. That is the file that I downloaded. I have not
> installed Jetty, does it come as part of the Windows Server or GeoServer
> installation? I have been able to extract the files from the .war file.
>
>
>
> Thanks for your help,
>
>
>
> Jerome
>
>
>
>
>
> *From:* Jonathan Moules [mailto:[email protected]]
> *Sent:* Thursday, October 31, 2013 5:04 AM
> *To:* [email protected]
> *Cc:* Jesse Eichar; Mauro Bartolomeoli; GeoServer Mailing List List
> *Subject:* Re: [Geoserver-users] GeoServer Printing Module
>
>
>
> Hi Jerome,
>
> Yep, this file:
>
>
> https://oss.sonatype.org/content/repositories/snapshots/org/mapfish/print/print-servlet/2.0-SNAPSHOT/print-servlet-2.0-SNAPSHOT.war
>
>
>
> If that's where you've put Tomcat/Jetty (I'm guessing Jetty as you windows
> installed), then yes, that's where you want to place the war file. Actually
> you'll probably want to extract it into that directory (it's basically a
> zip file with a different extension) and then delete the .war itself.
>
> After that you can access it in the way previously described.
>
> Regards,
>
> Jonathan
>
>
>
>
>
> On 30 October 2013 20:40, Jerome A. Wendell <[email protected]>
> wrote:
>
> Jonathan,
>
>
>
> The war file that I found at the link provided is
> print-servlet-2.0-SNAPSHOT.war. Is this the correct file?
>
>
>
> Also, the print directory that you suggested, would that be C:\Program
> Files (x86)\GeoServer 2.4.0\webapps\print?
>
>
>
> Thanks,
>
>
>
> Jerome
>
>
>
>
> This transmission is intended for the named addressee(s) only and may
> contain sensitive or protectively marked material up to RESTRICTED and
> should be handled accordingly. Unless you are the named addressee (or
> authorised to receive it for the addressee) you may not copy or use it, or
> disclose it to anyone else. If you have received this transmission in error
> please notify the sender immediately. All email traffic sent to or from us,
> including without limitation all GCSX traffic, may be subject to recording
> and/or monitoring in accordance with relevant legislation.
>
>
>
>
> This transmission is intended for the named addressee(s) only and may
> contain sensitive or protectively marked material up to RESTRICTED and
> should be handled accordingly. Unless you are the named addressee (or
> authorised to receive it for the addressee) you may not copy or use it, or
> disclose it to anyone else. If you have received this transmission in error
> please notify the sender immediately. All email traffic sent to or from us,
> including without limitation all GCSX traffic, may be subject to recording
> and/or monitoring in accordance with relevant legislation.
>
--
This transmission is intended for the named addressee(s) only and may
contain sensitive or protectively marked material up to RESTRICTED and
should be handled accordingly. Unless you are the named addressee (or
authorised to receive it for the addressee) you may not copy or use it, or
disclose it to anyone else. If you have received this transmission in error
please notify the sender immediately. All email traffic sent to or from us,
including without limitation all GCSX traffic, may be subject to recording
and/or monitoring in accordance with relevant legislation.
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
