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

[<tr...@do...>]

<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>Rob Vesse</td>
  </tr>
  <tr>
    <td><b>Date:</b></td>
    <td>2013-01-16 02:52 PM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Thanks for the patch, I revised it slightly and have included this in commit&nbsp;<a href="https://bitbucket.org/dotnetrdf/dotnetrdf/commits/7e644275430767c6ba96489a68c1568c9ebab66f">https://bitbucket.org/dotnetrdf/dotnetrdf/commits/7e644275430767c6ba96489a68c1568c9ebab66f</a></p>
<p>
	&nbsp;</p>
<p>
	This commit allows you to set a global static option Options.ForceHttpBasicAuth which will forcibly include the Authorization header in requests instead of relying on .Net to do HTTP challenge response so that users like yourself can turn this on if they need to workaround misbehaving servers.</p>
<p>
	&nbsp;</p>
<p>
	This will be incorporated in the next release which will hopefully be in the next week or so.</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>