2

I have a few hundred static HTML files that need to be processed.

They contain links like this

 <a href="http://www.mysite.com/">Link</a>

I need to add ?ref=self to any url that begins with http://www.mysite.com and becomes

<a href="http://www.mysite.com/?ref=self">Link</a>

however, I do not know whether it's going to be http://www.mysite.com or http://www.mysite.com/ also it could be linked to a sub directory.

What's the most efficient way to do this? in C#

Rana
  • 4,431
  • 9
  • 32
  • 39

3 Answers3

1

Parsing HTML can be tricky as HTML often contains poorly formed tags and attributes. I suggest looking into an existing HTML parsing library to do your heavy lifting, or, using XSLT to transform valid (x)HTML to your desired output.

This question What is the best way to parse html in C#? has some good links to HTML parsing libraries for C#.

Community
  • 1
  • 1
jscharf
  • 5,829
  • 3
  • 24
  • 16
1

What's the most efficient way to do this? in C#

  1. Look for the string http://www.mysite.com.
  2. If it doesn't exist, go to 7.
  3. Look for the next ".
  4. If it doesn't exist, error.
  5. Insert ?ref=self before the ".
  6. Go to 1.
  7. Return.

This can be accomplished with the following regular expression substitution:

s#http://www.mysite.com[^"]*#&?ref=self#g

A nicer (more expressive) way would be to use an HTML parser and XPath.

strager
  • 88,763
  • 26
  • 134
  • 176
  • Bug: The `href` attribute could be in single quotes ☺ – Timwi Aug 22 '10 at 05:46
  • @Timwi, That's not a bug. The OP clearly stated what the expected input is (which didn't include `'`), and that efficiency was a factor (so they say...). – strager Aug 22 '10 at 05:58
  • I don’t see where he stated that. The OP clearly stated that the expected input is **HTML**. He neither stated that it is a special subset of HTML, nor did he state that his examples are exhaustive. If I hadn’t commented, he might not have realised that any of his HTML files could contain href attributes with single quotes and that your algorithm would silently skip them. – Timwi Aug 22 '10 at 12:58
0

You could use Page.Request.UrlReferrer to detect where the request came from.

bjhamltn
  • 420
  • 5
  • 6