You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by mb...@comcast.net on 2008/02/08 22:13:21 UTC
managing user uploads best practices
What's the current wisdom on managing user uploaded files to a web app that's
deployed via a WAR?
In other words, when the WAR is updated, the directory containing uploaded files
would be wiped out.
Do people save uploaded files outside of the web app root directory? Security
issues with this?
Do people not use auto-expanding WAR files and manage the deployment by hand?
Do you not include the directory for uploaded files in the WAR (but create it at
runtime) and then trust that the expanded WAR won't overwrite it on deployment?
Any pointers greatly appreciated!
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: managing user uploads best practices
Posted by David Smith <dn...@cornell.edu>.
I certainly don't speak for everyone, but in the past I've either
provided an external folder for upload storage or a database. As far as
security goes, I don't see these being much if any different than
storing the files inside the webapp. In some ways you may get better
access control as the servlet serving them can be customized to provide
very fine grained access.
--David
mbeards@comcast.net wrote:
> What's the current wisdom on managing user uploaded files to a web app that's
> deployed via a WAR?
>
> In other words, when the WAR is updated, the directory containing uploaded files
> would be wiped out.
>
> Do people save uploaded files outside of the web app root directory? Security
> issues with this?
> Do people not use auto-expanding WAR files and manage the deployment by hand?
> Do you not include the directory for uploaded files in the WAR (but create it at
> runtime) and then trust that the expanded WAR won't overwrite it on deployment?
>
> Any pointers greatly appreciated!
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: managing user uploads best practices
Posted by Johnny Kewl <jo...@kewlstuff.co.za>.
---------------------------------------------------------------------------
HARBOR: http://coolharbor.100free.com/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
Making the Java dream come true.
---------------------------------------------------------------------------
----- Original Message -----
From: <mb...@comcast.net>
To: <us...@tomcat.apache.org>
Sent: Friday, February 08, 2008 11:13 PM
Subject: managing user uploads best practices
Yes... outside.
Its been a long long time now, vaguely remember struggling with Apache
uploader then eventually getting all to work...
Anyway... what I did is store the files in an Apache httpD folder, so I
could spy on the uploads, and they available for viewing again.
And whats cool is because Apache is also the load balancer in my case... can
have lots of TC's doing their thing.
I was making a kind of wiki thing for an estate agency... thats how I did
it.... way back when...
> What's the current wisdom on managing user uploaded files to a web app
> that's
> deployed via a WAR?
>
> In other words, when the WAR is updated, the directory containing uploaded
> files
> would be wiped out.
>
> Do people save uploaded files outside of the web app root directory?
> Security
> issues with this?
> Do people not use auto-expanding WAR files and manage the deployment by
> hand?
> Do you not include the directory for uploaded files in the WAR (but create
> it at
> runtime) and then trust that the expanded WAR won't overwrite it on
> deployment?
>
> Any pointers greatly appreciated!
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org