V2.2.7 Desktop Edition Problem - "No XML data in HTTP response"

Previous topic

Install & configuration

Next topic

Author	Message
Michael Meron	Tuesday 08 April 2003 3:10:24 am Hi all, I could need your help. The following is a bit lengthy but I thought you might need all that info in order to help me. This morning I had downloaded the Desktop Edition for eZ publish 2.2.7. After installation I tried it with the 'publishdemo.ez.no' test site and it worked, so I assume my DE installation is okay. So I bought a license. The license installation was easy and fine. I do not intend to use my DE for our intranetnet site, whose home page is located at 'http://naut.dewe.astrazeneca.net:81/op' (don't try to access it, you cannot reach it through our firewall). But horribly, every time I try to access our site through DE, I receive the error message, >>failed to access host "naut.dewe.astrazeneca.net:81". There was no XML data in the HTTP response.<< Needless to say that that the site is available and runs like a charm. This ist also not a DNS problem since I can ping our site, and a test with the IP address (instead of the name) yielded the same strange result. What I find interesting is the "Path" configuration variable in DE. It is nowhere documented, though I guess it is the key to solve my problem. For the publishdemo site, it contains the value "/xmlrpc", again, something that's not documented. Unfortunately this path does not work for my site (a pretty much default installation!) because there is no such directory!?!?!? I do have a ezxmlrpc directory, but this does not work. Sigh. Can someone help me, please. I am totally stuck, 50 dollars poorer than before, and don't know how to go on. Thank you very much indeed. --Michael
Gunnstein Lye	Tuesday 08 April 2003 3:45:12 am In short: If you use a virtual host apache config, enter "/xmlrpc" in the "Path" entry. The directory does not have to exist. If you don't use virtual host, enter "/index_xmlrpc.php". That file should exist in the eZ publish root directory. Note that your apache config must contain a rewrite rule for xmlrpc. I think this is mentioned in the docs. DE should connect through the same port as you use in your browser, you can set the port in the login dialog. DE works out-of-the-box on a standard eZ publish 2.2.7 installation, if you run an older version that may cause problems. regards
Michael Meron	Wednesday 09 April 2003 11:14:26 pm Gunnstein, >>If you don't use virtual host, enter "/index_xmlrpc.php". That file should exist in the eZ publish root directory.<< BINGO !!! :) Thank you SO very much indeed !! Two comments on this, however, if I may. (1) You may be interested to know that this does not (!) work in conjunction with a proxy server. I had to remove (!) the proxy server configuration in order to make DE work. Since our inTRAnet server is on "our" side of the firewall, this did not hurt. However, it is a very strange thing and you should definitely fix that. When hunting the bug, concentrate on proxy configuration when port# is not 80. (2) You may eventually want to include a documentation of the PATH variable with the DE download. To better understand the situation as it is right now, imagine you have bought a new car, but you cannot find the key. When you ask the vendor, he says, "Oh didn't I tell you, you must dance around the chimney of your house, four times at moonlight, and then a ghost will appear and give you the key." It should be easier than that. :) Thanks again for your help, and have a nice day, --Michael

Author

Message

Michael Meron

Tuesday 08 April 2003 3:10:24 am

Hi all,

I could need your help.

The following is a bit lengthy but I thought you might need all that info in order to help me.

This morning I had downloaded the Desktop Edition for eZ publish 2.2.7. After installation I tried it with the 'publishdemo.ez.no' test site and it worked, so I assume my DE installation is okay.

So I bought a license. The license installation was easy and fine.

I do not intend to use my DE for our intranetnet site, whose home page is located at 'http://naut.dewe.astrazeneca.net:81/op' (don't try to access it, you cannot reach it through our firewall).

But horribly, every time I try to access our site through DE, I receive the error message, >>failed to access host "naut.dewe.astrazeneca.net:81". There was no XML data in the HTTP response.<<

Needless to say that that the site is available and runs like a charm. This ist also not a DNS problem since I can ping our site, and a test with the IP address (instead of the name) yielded the same strange result.

What I find interesting is the "Path" configuration variable in DE. It is nowhere documented, though I guess it is the key to solve my problem. For the publishdemo site, it contains the value "/xmlrpc", again, something that's not documented. Unfortunately this path does not work for my site (a pretty much default installation!) because there is no such directory!?!?!? I do have a ezxmlrpc directory, but this does not work.

Sigh.

Can someone help me, please. I am totally stuck, 50 dollars poorer than before, and don't know how to go on. Thank you very much indeed.

--Michael

Gunnstein Lye

Tuesday 08 April 2003 3:45:12 am

In short:
If you use a virtual host apache config, enter "/xmlrpc" in the "Path" entry. The directory does not have to exist.

If you don't use virtual host, enter "/index_xmlrpc.php". That file should exist in the eZ publish root directory.

Note that your apache config must contain a rewrite rule for xmlrpc. I think this is mentioned in the docs.

DE should connect through the same port as you use in your browser, you can set the port in the login dialog.

DE works out-of-the-box on a standard eZ publish 2.2.7 installation, if you run an older version that may cause problems.

regards

Michael Meron

Wednesday 09 April 2003 11:14:26 pm

Gunnstein,

>>If you don't use virtual host, enter "/index_xmlrpc.php". That file should exist in the eZ publish root directory.<<

BINGO !!! :)

Thank you SO very much indeed !!

Two comments on this, however, if I may.

(1) You may be interested to know that this does not (!) work in conjunction with a proxy server. I had to remove (!) the proxy server configuration in order to make DE work. Since our inTRAnet server is on "our" side of the firewall, this did not hurt. However, it is a very strange thing and you should definitely fix that. When hunting the bug, concentrate on proxy configuration when port# is not 80.

(2) You may eventually want to include a documentation of the PATH variable with the DE download. To better understand the situation as it is right now, imagine you have bought a new car, but you cannot find the key. When you ask the vendor, he says, "Oh didn't I tell you, you must dance around the chimney of your house, four times at moonlight, and then a ghost will appear and give you the key."
It should be easier than that. :)

Thanks again for your help, and have a nice day,
--Michael

eZ debug

Timing:	Jan 31 2025 01:14:21
Script start
Timing:	Jan 31 2025 01:14:21
Module start 'layout'
Timing:	Jan 31 2025 01:14:21
Module start 'content'
Timing:	Jan 31 2025 01:14:22
Module end 'content'
Timing:	Jan 31 2025 01:14:22
Script end

Main resources:

Total runtime	1.0868 sec
Peak memory usage	8,192.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0046	588.6172	151.2734
Module start 'layout'	0.0046	0.0041	739.8906	220.7656
Module start 'content'	0.0087	1.0773	960.6563	4,420.5000
Module end 'content'	1.0860	0.0008	5,381.1563	11.7656
Script end	1.0868		5,392.9219

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0036	0.3320	16	0.0002
Check MTime	0.0013	0.1156	16	0.0001
Mysql Total
Database connection	0.0008	0.0710	1	0.0008
Mysqli_queries	0.9777	89.9573	57	0.0172
Looping result	0.0005	0.0474	55	0.0000
Template Total	1.0265	94.4	2	0.5132
Template load	0.0019	0.1742	2	0.0009
Template processing	1.0246	94.2741	2	0.5123
Template load and register function	0.0015	0.1358	1	0.0015
states
state_id_array	0.0011	0.1027	1	0.0011
state_identifier_array	0.0011	0.1044	2	0.0006
Override
Cache load	0.0016	0.1509	35	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0023	0.2073	2	0.0011
Fetch class attribute name	0.0021	0.1940	4	0.0005
XML
Image XML parsing	0.0085	0.7802	2	0.0042
class_abstraction
Instantiating content class attribute	0.0000	0.0010	4	0.0000
General
dbfile	0.0100	0.9166	16	0.0006
String conversion	0.0000	0.0008	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 14 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs