Introduction
I needed to attach files silently to HTML forms hosted in a WebBrowser
control without the user having to point to those files manually.
As you probably know, for security reasons, it is not possible to change the value of the HTML form file input programmatically. My first approach was to set focus on the input field and then do some SendKeys.SendWait()
calls to set the value. The field can be hidden away from screen by setting the absolute position and negative coordinates for it. Although it had some drawbacks, it worked fine in a stand-alone app, but unfortunately, inside a Word add-in, file inputs cannot receive keyboard input for some reason.
After examining the methods of the WebBrowser
, I found out that I can send arbitrary POST data using the Navigate()
method:
WebBrowser.Navigate(Uri url, string targetFrameName,
byte[] postData, string additionalHeaders)
There is a good example of how to make correct multipart request headers and body here, so I decided to use it. (You may also refer to RFC 1867.)
The solution: a helper class
To simplify the process of making requests, I wrote the helper class (included in the archive), so adding a file to the form can be as simple as:
private void webBrowser1_DocumentCompleted(object sender,
WebBrowserDocumentCompletedEventArgs e)
{
HtmlElement form = webBrowser1.Document.Forms[0];
form.AttachEventHandler("onsubmit", delegate(object o, EventArgs arg)
{
FormToMultipartPostData postData =
new FormToMultipartPostData(webBrowser1, form);
postData.SetFile("fileField", @"C:\windows\win.ini");
postData.Submit();
});
}
In the example above, I’m adding an event handler for the “onsubmit
” event, which intercepts the submit process, prepares new multipart POST messages with the actual data in the form, attaches a file to the input field with a specific name (“fileField
”), and then sends the result to the server (interrupting the original submit process).
Here’s a more complicated (and more correct) example, which manages several forms on one page (adding onsubmit
handler only for forms with a “multipart/form-data” enctype
attribute):
private void webBrowser1_DocumentCompleted(object sender,
WebBrowserDocumentCompletedEventArgs e)
{
HtmlDocument doc = webBrowser1.Document;
for (int i = 0; i < doc.Forms.Count; i++)
{
HtmlElement form = doc.Forms[i];
if (form.GetAttribute("enctype").ToLower() != "multipart/form-data") { continue; }
form.AttachEventHandler("onsubmit", delegate(object o, EventArgs arg)
{
FormToMultipartPostData postData =
new FormToMultipartPostData(webBrowser1, form);
postData.SetFile("file", @"C:\windows\win.ini");
postData.Submit();
});
form.SetAttribute("hasBrowserHandler", "1");
}
}
The FormToMultipartPostData
class (not the best name, I know), which does all the ‘dirty’ work, must be instantiated just before submitting a form.
From the constructor, it loads all the values set in the form (GetValuesFromForm()
method). The central method is GetEncodedPostData()
, which returns all the necessary parameters to make a POST request with WebBrowser.Navigate()
(header string and request body as a byte array). Submit()
is another convenience method to invoke WebBrowser.Navigate()
with the request data.
Because the class is rather large (compared to its modest functionality), I decided not to post it here. You can find it in the archive.
Handling JavaScript: form.submit()
By design, calling the submit()
method on a form in JavaScript does not fire the onsubmit
event, i.e., its handler will not be executed. To provide a work-around, I decided to set a handler for WebBrowser.Navigating
, which is invoked before the page location is changed:
private void webBrowser1_Navigating(object sender, WebBrowserNavigatingEventArgs e)
{
string url = e.Url.ToString();
if (url.StartsWith("submit:"))
{
string formId = url.Substring(7);
HtmlElement form = webBrowser1.Document.GetElementById(formId);
if (form != null) { form.RaiseEvent("onsubmit"); }
e.Cancel = true;
}
}
The trick is to set the window location to fake the URL which starts with “submit:” (the rest of this “pseudo-URL” is the form ID). If anyone knows a more elegant solution, please share it with me.
You may have noted in the above “complicated example” of adding an onsubmit
handler that there is an additional attribute to expose the presence of the handler to the JavaScript:
form.SetAttribute("hasBrowserHandler", "1");
Thus, the JavaScript code needed to invoke the submit process should be something like this:
function doSubmit(formId) {
var form = document.getElementById(formId);
if (form.getAttribute('hasBrowserHandler')) {
window.location = "submit:" + formId;
}
else {
form.submit();
}
}
The test script
I also included a PHP script which might be useful in testing and debugging the class.
Credits
Thanks to Steven Cheng from Microsoft, who posted an example of making multipart messages, I did not have to write the main (and most difficult) part of the code. There’s also an example of the same task done using the HttpWebRequest
class on CodeProject.
I hope this solution will help you save some time (I spend a whole day to find the best way to solve this simple task.) Since at this time I am a newbie to C#, any feedback is appreciated.