From: <tr...@do...> - 2013-01-15 21:50:42
|
<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 09:49 PM</td> </tr> <tr> <td><b>Comment:</b></td> </tr> <tr> <td colspan="2"><p> FYI - this patch to SesameHttpProtocolConnector.cs fixed the issue for us. Basically this forces authentication on every single HTTP request (so we never hit a 401 response unless the credentials were invalid):</p> <p> </p> <p> //Add Credentials if needed<br /> if (this._hasCredentials)<br /> {<br /> //NetworkCredential credentials = new NetworkCredential(this._username, this._pwd);<br /> //request.Credentials = credentials;<br /> string credentials = Convert.ToBase64String(ASCIIEncoding.ASCII.GetBytes(this._username+ ":" + this._pwd));<br /> request.Headers.Add("Authorization", "Basic " + credentials);<br /> }</p> <p> This obviously won't work in cases where other (non-Basic) authentication is in place (Digest, Negotiate, Kerberos, NTLM)..</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> |