top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Recommended way to setup file-uploading, in a Webdav based share

0 votes

I have been using a running HTTPD-server, that serves files via WebDAV. These files are then easily downloadable to any machines, which have the IP-Address of my running HTTPD server :)
Now, I need to add the ability for clients to upload files to the same WebDAV directory/virtualhost.
Nothing fancy, just an additional, simple, vanilla "Upload file to server" feature (preferably via the browser itself).

What is the recommended way to do this?

(I ask this, because on some googling, I found quite a few ways in the literature
* HTML form + client-side-script
* HTML form + server-side-script, etc).

The only constraint that I have is that I intend to use the Apache HTTPD-server.
Thus, it will be nice to hear some opinions on what is the most simple, reliable, robust way to implement this feature.

posted Jul 1, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

webDAV is used mainly for its writable features. For just serving files, you do not need it.
So, if you use webDAV clients, you should already be all set. The webDAV clients should be able to write files on the server.
"This extension to the HTTP protocol allows creating, moving, copying, and deleting resources and collections on a remote web server."

answer Jul 2, 2013 by anonymous
I had already checked that the server-directory is writable, by uploading a file via a small client-side python utility :)

However, my query is regarding what is the most recommended way to achieve this? :)

In particular, is it possible to get the uploading done, using a web-browser as the only client-side utility? (as that will do away with any needs of deploying any "special" client-side utility).

On some googling, I find that invoking a PHP-based-server-side-script from a HTML "Upload"-Form might do the job, but I am not sure if using PHP with "httpd" is recommended, as "mod_dav" already seems to do the server-side job.

Just a few starting-pointers on how to accomplish an "exclusive server-side solution, using only a browser at the client" will be greatly helpful :) :)
So you do not need webDAV. Just use apache to serve files + php for uploads
Similar Questions
+2 votes

Ive done several searches, and have found old and conflicting responses to the question of sharing a repository via NFS. So what is the current set of concerns with sharing repositories using NFS among several web servers?
Here is the scenario, several hundred repositories shared via NFS to a couple of webdav (Apache mod-svn) servers. The Apache servers set up via a round-robin DNS server (thus they are all sharing a common virtualhost name). All user access is via webdav (authentication and access controlled by an Apache authentication handler). The users will see a common hostname for all repositories. All the servers are "network close" to each other. Assuming that the NFS is current (NFS 4) with subtree checking disabled (as per the FAQ), are there any gotchas or other concerns.
I currently have a solution using some custom Apache proxying that is working, but Im looking at trying to simplify my solution.

+2 votes

Please tell us about the apache settings so that we can set the Proxytimeout to "each URL"?

timeout = 60

timeout = 300

0 votes

I am newbie in Apache concepts and only know Apache Tomcat. Following is my requirement, would anybody please help me how to setup.

I have a clustered JBOSS EAP 6.3 instances running on two different Windows 8 machines. Now I am planning to put a load balancer to dispatch the requests to these JBOSS clustered servers.

I am thinking of Apache httpds as a load balancer. What I got to know is these Apache web server will be available in source code and source code needs to be compiled as per the environment.

I am not finding any Windows 8 (64bit) Apache http installed in the Apache site. Would someone help me from where to download the Windows 8 (64bit) version of Apache httpd service.

And also any guide to setup the load balancer on Windows machine.

0 votes

I need to share data between sessions running in different Tomcat server.
I 'd been thinking about using a JMS broker (as ActiveMQ ):

  • when a new session is created in Tomcat A, it's created a new unique topic for this session
  • the session registers itself as listener of that topic ( the only one listener )
  • publish the name of this topic by some way , so it can be found by another session in Tomcat B

I don't know if somebody has used something like this sometime, and how he/she did it
Any suggestion/opinion ?

I'm not sure either use only one topic for all session created or one topic per session ?
I think that one topic per session is more safe because if I use one topic for all sessions, if one message is not read quickly by one consumer (a session ), could block the topic, Obviously , i'll define a TTL for messages/topic