- Thread starter
- #11
It must be something client side in WebEPG or something WebEPG does not do like pretending to be an IE browser.
Agent reference seems outdated.. but is it filtered on server-side?
HTTPTransaction.cs
Code:
public class HTTPTransaction
{
#region Variables
private string _agent = "Mozilla/4.0 (compatible; MSIE 6.0; WindowsNT 5.0; .NET CLR 1 .1.4322)";
Wget didn't have any problem:
Wget normally identifies as `Wget/version', version being the current version number of Wget.
It might be also something to do with how the url is processed in these classes.