OK, so here's the scenario:
1. upgraded Mac to OS X 10.9 (currently 10.9.1, in fact)
2. re-installed latest PrinceXML
3. tried creating test PDF files from command line with: prince http://testurl -o test.pdf -v
4. output was as follows
prince: Loading document...
prince: loading document: http://testurl/test.html
prince: loading HTML5 input: http://testurl/test.html
prince: loading document: http://testurl/test.html
prince: http://testurl/test.html: error: couldn't connect to host
prince: http://testurl/test.html: error: could not load input file
prince: error: no input documents to process
5. ran curl against same URL, works fine
6. checked logs - apache isn't even firing up when Prince runs
7. ran prince against daringfireball.net - works fine
The page loads OK in the browser - I had to fix a couple of things with the Apache config as Apple loves breaking it between versions, but I cannot detect a single reason why this might be failing.
1. upgraded Mac to OS X 10.9 (currently 10.9.1, in fact)
2. re-installed latest PrinceXML
3. tried creating test PDF files from command line with: prince http://testurl -o test.pdf -v
4. output was as follows
prince: Loading document...
prince: loading document: http://testurl/test.html
prince: loading HTML5 input: http://testurl/test.html
prince: loading document: http://testurl/test.html
prince: http://testurl/test.html: error: couldn't connect to host
prince: http://testurl/test.html: error: could not load input file
prince: error: no input documents to process
5. ran curl against same URL, works fine
6. checked logs - apache isn't even firing up when Prince runs
7. ran prince against daringfireball.net - works fine
The page loads OK in the browser - I had to fix a couple of things with the Apache config as Apple loves breaking it between versions, but I cannot detect a single reason why this might be failing.