I’ve been working on a program that needs to parse a html file for form data. So when I was deciding what method to use, a few popped right into my mind.
The first being a character by character search through the string. Parsing through the data and flagging sections that fit the signature of what was being searched for.
The second would be automating that by using the built-in string functions to split up the string and drill down until the needed data was extracted.
The third, and one I chose to use, was with regular expressions. This in my mind is the most “poetic” method of the three, which would allow me to make the a robust and reliable function.
While I’ve used regular expressions a lot throughout the years. I never seem to remember enough to construct a decent statement. I had recently bought a pocket reference (link below), so I used that to get a statement constructed. It had a total of about 6 pages for C#, but I pretty much got what I needed from it. Anything else I just searched the Internet for.
Included below is most of the code to extract an unlimited number of forms from a html document:
returnHtmlFormData = new List<HtmlForm>();
// Take the initial response text and process it for FORM tags, this can handle an "unlimited" number of them
// Regular expression to extract each form tag as well as the action attribute [0] and [1] in the group collection
Regex formExtractor = new Regex(@"<form\b[^>]*action=""?(.*?)[""|\s].*?>.*?</form>", RegexOptions.IgnoreCase | RegexOptions.Compiled | RegexOptions.Singleline);
// Regular expression to extract all of the input tags (we want the name and the value of each)
Regex inputTagExtractor = new Regex(@"<input\b[^>]*name=""?(.*?)[""|\s].*?value=""?(.*?)[""|\s].*?[/??|>]", RegexOptions.IgnoreCase | RegexOptions.Compiled | RegexOptions.Singleline);
List<HtmlForm> is a collection of a class that I created. It basically just stores:
1. The action page, which we would need if we want to use this data later to send a POST.
2. All of the fields that were in the form.
The two Regex instances are what do all of the work here. The first searches the text for form tags. It takes into account quite a few possibilities like if there are spaces or property fields in the starting tag. Also, notice the three regex options. Ignoring case is obvious, compiled helps improve execution time, and the singleline option means the regex expression engine will consider “character return” and “line feed” as normal white-space.
The second searches within the form tag (as shown later on) for all input fields). It uses the parenthesis characters to save certain pieces of the data into a buffer called a GroupCollection we will look at later. It also takes into account things like if properties have or do not have quotes around their values.
//attempt to extract out all forms in the passed stringThis line above takes some text data and performs the first regular expression on it. It returns all instances of a match back in a MatchCollection object.
As you can see above, I use my List collection returnHtmlFormData to hold a list of classes… of my special form storage class. I’ll let my code comments above speak for themselves, but basically you start from a MatchCollection, from there you loop through as single items of class Match, each Match can then be processed further by reading the GroupCollection for the actual data we wanted extracted. It’s quite and ingenious construct of classes, but it took be a while to figure out…
Amazon.com Book Link:
Regular Expression Pocket Reference: Regular Expressions for Perl, Ruby, PHP, Python, C, Java and .NET