Hello,
I get this message displayed in the center of the converted PDF document:

The form cannot be displayed in the browser because
the use of session cookies has been disabled in the
current browser settings. In order to load the form,
session cookies must be allowed.


The PDF shows the navigation around the top and left but the InfoPath web form is not showing, shows the message where the form should be. Do you have any idea why only the InfoPath part of the page does not render?

All other aspects of the page seem to render fine. Here is the source:

protected void Button1_Click(object sender, EventArgs e)
{
var url = "https://sharepoint.domain.nam/path_to_list/editifs.aspx?ID=500";

HtmlToPdfOptions options = new HtmlToPdfOptions();
// Fiddler - attempt at reading header cookie - no good
// System.Net.Cookie cookie1 = new System.Net.Cookie("_InfoPath_Canary", "AELSAZT3NT4TYS4AME6NWTFMOLACML2MNFZXI4ZPINUGC3T
// HMVJGK4LVMVZXIL2JORSW2L3UMVWXA3DBORSS46DTNYUGQNRTMRTUIYLTJU2UOMSWGR4ECWDXJVVECWSFMVSFQTKVKNXUUSTZNRCGO2KLKJVQ");
// options.Cookies.Add(cookie1);

HttpResponse response = HttpContext.Current.Response;
response.Clear();
response.ClearHeaders();
response.ContentType = "application/pdf";
options.SSLVerificationMode = SSLVerificationMode.None;
options.ZoomLevel = (float) .5; // this works
options.NoLink = false; // this works too
options.NoCache = true;
options.UserName = "domain\\User";

options.Password = "password";
//Convert to the output stream
EO.Pdf.HtmlToPdf.ConvertUrl(url, response.OutputStream,options);

response.End();

}

Ok I think I understand. Your product, when used server-side to consume a specified URL, does not interact with the assigned web site the same way a client side web browser would. I have to assume that an exact rendering (in memory) of the page contents would be necessary to reproduce the contents to a PDF. We may have to wait until your product has the ability to replicate all aspects of browser rendering before we decide to use it for SharePoint, however it may be acceptable for static html pages.

"almost" is a huge difference. You see, I never have to use fiddler to find cookies when I am using the application in my browser client, and I never see session errors. It is OK that your product is not completely compatible to SharePoint list forms right now, keep working on it - you are close.