This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit

eZ Community » Forums » Developer » Webdav and eZ 4.1.1? (404 error)

Webdav and eZ 4.1.1? (404 error)

Webdav and eZ 4.1.1? (404 error)

Monday 04 January 2010 12:30:22 am - 10 replies


I am struggling with setting up a webdav connection in eZ 4.1.1, but cant get it to work properly.

I am finished with setting up the virtual host with separate dns. Also, I have enabled webdav in the webdav.ini file.

When connecting I can see the siteaccesses in the webdav client. When clicking on a siteaccess, I see:

  • Content
  • Media

However, as the site is in Swedish, the node names are:

  • Innehåll (meaning content)
  • Media (same as in english)

When clicking Media, it seems as the client moves down to the media folder, however nothing is visible, the folder shows up empty.

Even worse - when clicking on Innehåll (content), I immediately get the error 404.

What do you think, can this be a bug due to the swedish character 'å' in the Innehåll (content) node? Or does anyone have another idea on what might be going wrong here? I am really out of ideas right now so every thougth is appreciated.

Best regards,


Wednesday 06 January 2010 2:08:08 pm

Hello Nicklas

I am guessing you use Internet Explorer as a webdav client ?

I already had problems with last versions of IE and webdav because it REALLY doesn't like special chars... This stopped me using Webdav against MultiFileUpload extension...

Thursday 07 January 2010 10:13:14 am

Hello again,

Thanks for your reply, Jérôme. However, I have tried several Windows and Linux based clients with the same result.

I have now found the core of the problem.

It´s in row 3177 (public static function virtualContentFolderName()) of the file kernel/private/classes/webdav/ezwebdavcontentbackend.php.

I have been wondering where the virtual content folder were translated to the swedish word for Content - "innehåll", and this row takes care of that:

return ezi18n( 'kernel/content', 'Content' );

However, since the content node is NOT translated in the systems database, a subequent call to /webroot/Innehåll will render a 404 error. The call has to be done to /webroot/Content, of course. As Content is the name of the node.

I changed the line to

return  'Content';

And now it is working. So far... Also, the Media folder is empty in webdav. Thats my next problem... It´s obvious that the webdav functionality isn´t ready for commercial use in the shape it´s in today.

Best regards,


Thursday 07 January 2010 11:10:18 am

I'm happy you found the origin of this problem... Can you please report this bug on the issue tracker ?

Curiosity : Which webdav clients did you try ?

Monday 11 January 2010 10:09:04 pm

Hi Jérôme,

I have replicated the issue of not seeing the 'Media' folder in webdav and have added a ticket:

FWIW I used the following clients with the same result:

Konqueror 4.1.3 (Linux FC9)
WebDrive 9.1 (Win XP SP3)
NetDrive (Win XP SP3) 

Cheers Russ

Modified on Monday 11 January 2010 10:11:20 pm by Russell Michell

Tuesday 12 January 2010 12:12:33 am

Hi Russel and Jérôme!

Sorry for the delay with my response about this issue. It appears to be a never ending quest to make Webdav work on eZ 4.1.1.

I have been occupied with continuous reserach for error after error appearing...

As I mentioned above, I couldnt see anything below the virtual Media node. This took a while to sort out, but I have now solved the problem. It turned out to be a mismatch in constants names. Let me be more specific.

Have a look at the file kernel/private/classes/webdav/ezwebdavcontentbackend.php

Right after the class definition we have code setting constants like this:

/**     * The name of the content folder in eZ Publish.     */
/**     * The name of the media folder in eZ Publish.     */

From this one could assume that these constants would be used when referencing the virtual folders in webdav. And my experience until now is that the constants are also used to fetch nodes from the Db (correct me if I am wrong...)

If so, since we are in eZ 4, the media folder should be referenced 'media', not 'Media'.

I changed this, but nothing happened. After a long adventure into the ezc/Webdav I found my way back to row 3182 in kernel/private/classes/webdav/ezwebdavcontentbackend.php

/**     * The name of the media folder in eZ Publish, translated.
* @return string
public static function virtualMediaFolderName()    {
return ezi18n( 'kernel/content', 'Media' );    }
/**     * The name of the media folder in eZ Publish, translated.
* @return string

Please note that the Media folder name is hardcoded here. I wonder why the constant mentioned above wasnt used....

Also, here as well, Media, when is should have been media...

Another thing, I dont understand how the ezi18n can be right to use here. See my problem with the content node above in this thread.

Maybe I just dont understand, but how can it be correct to translate the node and then later on try to fetch from the db the translated value? It surely is not translated there...

After my corrections, I got the Media part working but there were more problems to come.

Let me get back with more info, but the function internalNodePath in the same file is a little worrying.To begin with, also here the Media folder is hardcoded as a string. However here with the correct format.

But I am more troubled with the way the method returns paths, primarily in the media part.In our system we use pathprefixes, set up in Site.ini.

The code cant possibly be written with pathprefixes in mind. At least I couldnt publish anything with webdav to the media folder without tweaking this function. I will get back with more info when I am sure of what I am doing... happy.gif Emoticon

Also - please note that if you are using pathprefixes, you MUST use


In your override/site.ini. Otherwise it wont work.

The need for the PathPrefixExclude should really be mentioned in the documentation. I havent seen a trace of it anywhere...

So - is that it?

Not by far, I am afraid.

Now I am struggling with problems moving and copying nodes in webdav.

Both these actions do work - the node gets copied or gets moved. However, in the same process the webserver returns a HTTP 500 status, like this:

(Moving an image, apache access log) - user [11/Jan/2010:23:51:29 +0100] "MOVE /customer/media/bilder/bild_3.png HTTP/1.1" 500 69 "-" "Microsoft Data Access Internet Publishing Provider DAV 1.1"

So the move action, consisting of a copy action followed by a delete action works perfectly. But what is it that is sending the 500 "Internal Server Error" repsonse code? I dont have a clue and it is driving me crazy...

All ideas that might lead in whatever useful direction are welcome... And as you all can see, the webdav functionality in eZ is far from ready for your customer project.

To be continued...

Best regards


Modified on Tuesday 12 January 2010 12:18:03 am by Nicklas Lundgren

Tuesday 12 January 2010 9:08:44 am

Hi Nicklas

I think it would be useful that you add a comment in the issue blunk.gif Emoticon

Tuesday 12 January 2010 10:25:32 am

Hi Jérôme,

Yes, I will add to Russels issue when I have the full picture of the problems.

Tuesday 16 March 2010 10:51:28 pm

Hi there Nicklas,

Have you got any more of your WebDAV findings to add to the ticket? (

Please do add them to the ticket so the eZ dev's have lots of info to work from.


Thursday 18 March 2010 2:09:20 am

For those struggling to get WebDAV to work, and all you needed if for was multi-file upload. Look at the ezmultiupload extension.

It works great.

I added some patches in the forum to enable user-selected upload destinations, which may or may not make it (in a slightly more refined form) to the main project.


Thursday 18 March 2010 10:52:10 am

If ezmultiupload doesn't work for you because of too large size files, take a look at


You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from