This actually depends on the update/upgrade scheme you have conceived.
Option I:
User uploads firmware via the web from his desktop. Then you would
need to do what you are asking for i.e upload using HTTP.
Option II:
User logs on to the Web UI on the box and clicks a "Download Firmware"
button which will fetch the image from a known location or a location
given by the user on the webpage. This will invoke wget/curl
internally to download the image. If it is asynchronously spawned,
you'll need to look at refreshing the page with a log output to give a
semblence of synchrony.
Can you not execute wget or curl using CGI on the box using the same
webserver you have currently? This way, your older CGI scripts will
still work and you will have a working mechanism.
-- Mohan Sundaram
On Thu, Jul 2, 2009 at 1:53 PM, Krishna<mail2krish@xxxxxxxxx> wrote:
On Thu, Jul 2, 2009 at 3:24 AM, Mohan Sundaram <mohan.tux@xxxxxxxxx> wrote:
IMHO, fetching the images using these utilities on the box is a better
approach than trying to upload an image using http(s). Further, these
utilities support retries/ resumes which will be useful in times of
flaky access.
Like I told I already have some few CGI scripts running in the web server,
when i tried to add a web based firmware upgrade feature i found the big
file upload problem, I cannot do a netcat if in that case my other CGI
scripts cannot be handled. security is not an issue here. I wanted to know
if any one has worked in any embedded web server for uploading huge files,
so that I can rely on the fact and try that.
Bye,
Krishna.
_______________________________________________
To unsubscribe, email ilugc-request@xxxxxxxxxxxxx with
"unsubscribe <password> <address>"
in the subject or body of the message.
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
