Definitely, please explain more clearly what you are actually hoping to do.
But I can offer some cautions. A web server is not a file server. When you use an http: URL to access a "file", what you are actually doing is requesting that the web server should locate or construct the resource (the "R" in URL) and send a copy of the resource data to your client program. If you want to save that resource as a local file, that's fine, but the resource data itself is not a file.
If you set the right headers in the URL response stream, and your client is configured to be agreeable, you will be prompted to save the resource data in a file at a location that you specify in the pop-up "File Save As..." dialog (assuming a GUI client like a web browser). Depending on the OS and client app (and its settings), you may see a default save file name/path pre-loaded into that dialog.
You cannot have the server force a file to save to a specific location. In fact, you cannot have the server force a file to be saved at all. That would not only be rude, and non-portable ("C:\some directory\file.txt" doesn't work too well on my Linux machine), it would also be how a server could be used to inject malware onto a client. So instead the client has to actively participate in the process. Sadly, all too many clients have users who will happily download malware on their own, but that's a different story.
"privilege" comes from the Latin words for "private" and "law" (legal) and dates to feudal times. To "claim privilege" meant that you were above the laws that applied to the common people.
posted 1 week ago
Tim Holloway wrote:Definitely, please explain more clearly what you are actually hoping to do.
I got it figured out. Thanks for steering me in the right direction. Here is the code I used.
I have always wanted to have a neighbor just like you - Fred Rogers. Tiny ad:
Try Free Java/.NET Libraries for Word Excel PowerPoint and PDF