[dotNetRDF-Develop] Issue CORE-301 has a new comment

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

<p>A new comment has been added to the following issue.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>SPARQL update fails against Sesame Endpoint secured with Basic HTTP Authentication</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Core Library (dotNetRDF.dll)</td>
  </tr>
  <tr>
    <td><b>Created By:</b></td>
    <td>Daeron Meyer</td>
  </tr>
  <tr>
    <td><b>Date:</b></td>
    <td>2013-01-15 06:50 PM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	After looking at your fiddler trace I think that it might be some sort of issue with Tomcat not dealing well with the Expect: 100-continue header as part of the second authenticated HTTP/1.1 POST request. I&#39;ve seen similar issues that were only addressed recently in other HTTP servers (Example: http://wiki.squid-cache.org/Features/HTTP11 )</p>
<p>
	But if that&#39;s the case, then I&#39;m not sure why the latest version of the Sesame release would fix it other than perhaps they did something to tweak Tomcat behavior to better handle that. Unfortunately using the latest version of Sesame may not work for us since we are using a modified version of the Sesame release from Ontotext (as part of OWLIM) but I&#39;ll see if Ontotext has plans to upgrade and/or see if I can tweak the released version to work (by comparing it to the latest Sesame release).</p>
<p>
	This has been very helpful. Thanks again!</p></td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=301" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=301</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>