Menu
▾
▴
dotnetrdf-develop — Developer Discussion and Feature Request
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
(11) |
Mar
(17) |
Apr
(12) |
May
(2) |
Jun
(20) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(5) |
| 2011 |
Jan
(4) |
Feb
(1) |
Mar
(2) |
Apr
(2) |
May
(5) |
Jun
|
Jul
(12) |
Aug
(4) |
Sep
(5) |
Oct
(1) |
Nov
(38) |
Dec
(27) |
| 2012 |
Jan
(46) |
Feb
(182) |
Mar
(83) |
Apr
(22) |
May
(68) |
Jun
(47) |
Jul
(135) |
Aug
(84) |
Sep
(57) |
Oct
(45) |
Nov
(27) |
Dec
(61) |
| 2013 |
Jan
(59) |
Feb
(78) |
Mar
(66) |
Apr
(107) |
May
(27) |
Jun
(56) |
Jul
(53) |
Aug
(3) |
Sep
(19) |
Oct
(41) |
Nov
(44) |
Dec
(54) |
| 2014 |
Jan
(49) |
Feb
(72) |
Mar
(22) |
Apr
(41) |
May
(63) |
Jun
(27) |
Jul
(45) |
Aug
(12) |
Sep
(3) |
Oct
(8) |
Nov
(27) |
Dec
(16) |
| 2015 |
Jan
(3) |
Feb
(20) |
Mar
(6) |
Apr
(4) |
May
(15) |
Jun
(2) |
Jul
(4) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(16) |
May
(9) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
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>
|
|
From: <tr...@do...> - 2013-01-15 19:34:18
|
<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 07:33 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
It seems others have run into similar issues with Tomcat:</p>
<p>
https://issues.apache.org/bugzilla/show_bug.cgi?id=49779</p>
<p>
http://tomcat.10.n6.nabble.com/501-Method-not-implemented-with-successive-POST-requests-td2175296.html</p>
<p>
Also, apparently there is a way for control to be passed to the servlet when encountering the Expect: 100-continue request using filters/valves:</p>
<p>
http://grokbase.com/t/tomcat/users/116jekrajq/allow-servlet-to-control-100-continue-response</p>
<p>
So perhaps this is what the more recent version of Sesame is doing. In any case, feel free to close this bug request as it does not seem to be an issue with the openrdf cilent libraries at this point.</p>
<p>
</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>
|
|
From: <tr...@do...> - 2013-01-15 18:50:57
|
<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'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's the case, then I'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'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>
|
|
From: <tr...@do...> - 2013-01-15 17:05:30
|
<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>Aggregates applied over empty results give incorrect answers</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-15 05:04 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
A sequence of unit tests were added to confirm that this was the case as well as fixes to correct the problem.</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=304" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=304</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>
|
|
From: <tr...@do...> - 2013-01-15 17:04:59
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Aggregates applied over empty results give incorrect answers</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "In Progress" to "Completed"
</li>
<li>Resolution changed from "none" to "Fixed"
</li>
<li>Progress changed from "2,000.00 %" to "10,000.00 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=304" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=304</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>
|
|
From: <dot...@li...> - 2013-01-15 16:56:09
|
Send dotNetRDF-commits mailing list submissions to dot...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits or, via email, send a message with subject or body 'help' to dot...@li... You can reach the person managing the list at dot...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of dotNetRDF-commits digest..." Today's Topics: 1. commit/dotnetrdf: 2 new changesets (Bitbucket) 2. commit/dotnetrdf: rvesse: Merge latest changes from default to 1.9 branch (Bitbucket) 3. commit/dotnetrdf: rvesse: Adjust GraphCollection and BaseGraphCollection to match revised IGraphCollection interface (Bitbucket) 4. commit/dotnetrdf: rvesse: Fix up WrapperGraphCollection to align with IGraphCollection changes (Bitbucket) 5. commit/dotnetrdf: rvesse: Make a couple of error messages more friendly (Bitbucket) 6. commit/dotnetrdf: 2 new changesets (Bitbucket) 7. commit/dotnetrdf: rvesse: PreAuthenticate not supported under Silverlight (CORE-302) (Bitbucket) 8. commit/dotnetrdf: 3 new changesets (Bitbucket) 9. commit/dotnetrdf: 2 new changesets (Bitbucket) 10. commit/dotnetrdf: 6 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Mon, 07 Jan 2013 10:57:38 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0a9efb021a97/ changeset: 0a9efb021a97 user: rvesse date: 2013-01-07 11:56:11 summary: Add missing license headers affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/68500024a8c0/ changeset: 68500024a8c0 user: rvesse date: 2013-01-07 11:57:28 summary: Note recent bug fixes in Change Log affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Wed, 09 Jan 2013 15:27:08 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Merge latest changes from default to 1.9 branch To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/78025e21cb9b/ changeset: 78025e21cb9b branch: 1.9 user: rvesse date: 2013-01-09 16:26:54 summary: Merge latest changes from default to 1.9 branch affected #: 1934 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 3 Date: Wed, 09 Jan 2013 15:59:19 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Adjust GraphCollection and BaseGraphCollection to match revised IGraphCollection interface To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/603dde1dac4a/ changeset: 603dde1dac4a branch: 1.9 user: rvesse date: 2013-01-09 16:59:05 summary: Adjust GraphCollection and BaseGraphCollection to match revised IGraphCollection interface affected #: 6 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 4 Date: Wed, 09 Jan 2013 16:04:51 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Fix up WrapperGraphCollection to align with IGraphCollection changes To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8d820c3d8501/ changeset: 8d820c3d8501 branch: 1.9 user: rvesse date: 2013-01-09 17:04:40 summary: Fix up WrapperGraphCollection to align with IGraphCollection changes affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 5 Date: Wed, 09 Jan 2013 16:14:14 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Make a couple of error messages more friendly To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b9504f6a139a/ changeset: b9504f6a139a user: rvesse date: 2013-01-09 17:08:55 summary: Make a couple of error messages more friendly affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 6 Date: Tue, 15 Jan 2013 10:37:26 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/87080537c60f/ changeset: 87080537c60f user: rvesse date: 2013-01-15 11:34:51 summary: Enable PreAuthenticate for various Store connectors (CORE-301, CORE-302) affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/7983036d9f5c/ changeset: 7983036d9f5c user: rvesse date: 2013-01-15 11:37:15 summary: Enable PreAuthenticate for SparqlRemoteEndpoint and SparqlRemoteUpdateEndpoint (CORE-301, CORE-302) affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 7 Date: Tue, 15 Jan 2013 10:54:06 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: PreAuthenticate not supported under Silverlight (CORE-302) To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/94098cc7899c/ changeset: 94098cc7899c user: rvesse date: 2013-01-15 11:40:39 summary: PreAuthenticate not supported under Silverlight (CORE-302) affected #: 6 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 8 Date: Tue, 15 Jan 2013 13:06:09 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 3 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9a4d44ad3296/ changeset: 9a4d44ad3296 user: rvesse date: 2013-01-15 13:52:00 summary: Upgrade VDS.Common to 1.1.2 affected #: 14 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0eba975863a0/ changeset: 0eba975863a0 user: rvesse date: 2013-01-15 13:54:10 summary: Upgrade VDS.Common to 1.1.2 affected #: 7 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6b2a570ebd82/ changeset: 6b2a570ebd82 user: rvesse date: 2013-01-15 14:05:56 summary: Upgrade VDS.Common to 1.1.2 affected #: 3 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 9 Date: Tue, 15 Jan 2013 16:32:57 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/92eb8861a5ac/ changeset: 92eb8861a5ac user: rvesse date: 2013-01-15 17:31:59 summary: Initial tests and fix for a bug in aggregates applied over empty results (CORE-304) affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6e1e6a355adc/ changeset: 6e1e6a355adc user: rvesse date: 2013-01-15 17:32:47 summary: Another variation on the test (CORE-304) affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 10 Date: Tue, 15 Jan 2013 16:56:00 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 6 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 6 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e7cdf7e21cc9/ changeset: e7cdf7e21cc9 user: rvesse date: 2013-01-15 17:44:44 summary: Tests which illustrate SUM over empty results is currently broken (CORE-304) affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0c228438c4a2/ changeset: 0c228438c4a2 user: rvesse date: 2013-01-15 17:45:57 summary: Fix for bug in SUM over empty results (CORE-304) affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f4f4458ab666/ changeset: f4f4458ab666 user: rvesse date: 2013-01-15 17:47:42 summary: Tests which illustrate AVG over empty results is currently broken (CORE-304) affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3f114dfa3de4/ changeset: 3f114dfa3de4 user: rvesse date: 2013-01-15 17:48:27 summary: Fix for bug in AVG over empty results (CORE-304) affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/15568ea88bfc/ changeset: 15568ea88bfc user: rvesse date: 2013-01-15 17:50:35 summary: Add tests which validate that behaviour for MIN and MAX over empty results is already correct (CORE-304) affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/74b77c7589ff/ changeset: 74b77c7589ff user: rvesse date: 2013-01-15 17:55:46 summary: Tests and bug fix for GROUP_CONCAT over empty results (CORE-304) affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 4, Issue 2 *********************************************** |
|
From: <tr...@do...> - 2013-01-15 16:35:23
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Aggregates applied over empty results give incorrect answers</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Confirmed" to "In Progress"
</li>
<li>Progress changed from "0.00 %" to "2,000.00 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=304" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=304</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>
|
|
From: <tr...@do...> - 2013-01-15 16:35:03
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Aggregates applied over empty results give incorrect answers</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>Milestone:</b></td>
<td>0.9.0 RC 4</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>High</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Some aggregates now give the wrong answers when applied over an empty multiset, this is likely a by-product of the GROUP BY refactoring. Fixing this looks to be relatively simple</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=304" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=304</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>
|
|
From: <tr...@do...> - 2013-01-15 16:14:28
|
<p>The following issue has been updated by Rob Vesse:</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 colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Assigned to changed from "none" to "Rob Vesse"
</li>
</ul>
</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>
|
|
From: <tr...@do...> - 2013-01-15 16:11:20
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Provide a Portable Class Library build of dotNetRDF</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>Milestone:</b></td>
<td>Unscheduled</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Build, Release and Testing</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Normal</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Improvement</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Kal is currently looking into the feasbility of creating a Portable Class Library build of dotNetRDF</p>
<p>
</p>
<p>
NB - Some necessary pre-cursor work to this has been done already by providing a PCL build of VDS.Common</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=303" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=303</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>
|
|
From: <tr...@do...> - 2013-01-15 16:09:41
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Use PreAuthenticate for all HTTP operations</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Planned" to "Completed"
</li>
<li>Resolution changed from "none" to "Completed"
</li>
<li>Progress changed from "0.00 %" to "10,000.00 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=302" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=302</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>
|
|
From: <tr...@do...> - 2013-01-15 16:09:36
|
<p>The following issue has been updated by Rob Vesse:</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 colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Confirmed" to "In Progress"
</li>
<li>Progress changed from "0.00 %" to "5,000.00 %"
</li>
</ul>
</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>
|
|
From: <tr...@do...> - 2013-01-15 11:11:13
|
<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-15 11:10 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Just upgraded to the latest Sesame release (2.7.0-beta1) and this now works without a problem. Interestingly in the ReadMe for this release (<a href="http://sourceforge.net/projects/sesame/files/Sesame%202/2.7.0-beta1/">http://sourceforge.net/projects/sesame/files/Sesame%202/2.7.0-beta1/</a>) includes the following line item:</p>
<p>
<span style="color: rgb(85, 85, 85); font-family: monospace; font-size: 13px; line-height: 18px; white-space: pre-wrap; ">Multiple large improvements in the OpenRDF Workbench, including support for basic HTTP authentication, paging support of query results, and bookmarking of queries.</span></p>
<p>
This would tend to suggest to me that there may have been some issues with HTTP authentication in the past. I will file a bug against Sesame regardless and let them investigate further.</p>
<p>
</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>
|
|
From: <tr...@do...> - 2013-01-15 11:00:04
|
<p>The following issue has been updated by Rob Vesse:</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 colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "New" to "Confirmed"
</li>
<li>Milestone changed from "none" to "0.9.0 RC 4"
</li>
<li>Affected Milestone changed from "0.9.0 RC 4" to "0.8.2 RC 3"
</li>
</ul>
</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>
|
|
From: <tr...@do...> - 2013-01-15 10:55:35
|
<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-15 10:54 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Ok, so I have now debugged with Fiddler with PreAuthenticate enabled and I still see the same behaviour so I'm now once again of the opinion that this looks to be a Sesame/Tomcat bug. In the Fiddler output I see the following request made by dotNetRDF:</p>
<p>
</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
POST http://localhost:8080/openrdf-sesame/repositories/update-me/statements HTTP/1.1</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Accept: */*</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Content-Type: application/x-www-form-urlencoded</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Host: localhost:8080</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Content-Length: 343</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Expect: 100-continue</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; min-height: 9px; ">
</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
update=PREFIX+rdf%3a+%3chttp%3a%2f%2fwww.w3.org%2f1999%2f02%2f22-rdf-syntax-ns%23%3e%0d%0aPREFIX+rdfs%3a+%3chttp%3a%2f%2fwww.w3.org%2f2000%2f01%2frdf-schema%23%3e%0d%0aPREFIX+xsd%3a+%3chttp%3a%2f%2fwww.w3.org%2f2001%2fXMLSchema%23%3e%0d%0aINSERT+DATA%0d%0a%7b+%3chttp%3a%2f%2fx%2f%3e+%3chttp%3a%2f%2fy%2f%3e+%3chttp%3a%2f%2fz%2f%3e+.+%7d%0d%0a</p>
<p>
This gets the 401 Unauthorized like so:</p>
<p>
</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
HTTP/1.1 401 Unauthorized</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Server: Apache-Coyote/1.1</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
WWW-Authenticate: Basic realm="Sesame server configuration"</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Content-Type: text/html;charset=utf-8</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Content-Length: 954</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Date: Tue, 15 Jan 2013 10:46:06 GMT</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; min-height: 9px; ">
</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
<html><head><title>Apache Tomcat/7.0.26 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 401 - </h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>This request requires HTTP authentication ().</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.26</h3></body></html></p>
<p>
So then dotNetRDF resends the request with the Authentication header included:</p>
<p>
</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
POST http://localhost:8080/openrdf-sesame/repositories/update-me/statements HTTP/1.1</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Accept: */*</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Content-Type: application/x-www-form-urlencoded</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Authorization: Basic YWRtaW46cGFzc3dvcmQ=</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Host: localhost:8080</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Content-Length: 343</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Expect: 100-continue</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; min-height: 9px; ">
</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
update=PREFIX+rdf%3a+%3chttp%3a%2f%2fwww.w3.org%2f1999%2f02%2f22-rdf-syntax-ns%23%3e%0d%0aPREFIX+rdfs%3a+%3chttp%3a%2f%2fwww.w3.org%2f2000%2f01%2frdf-schema%23%3e%0d%0aPREFIX+xsd%3a+%3chttp%3a%2f%2fwww.w3.org%2f2001%2fXMLSchema%23%3e%0d%0aINSERT+DATA%0d%0a%7b+%3chttp%3a%2f%2fx%2f%3e+%3chttp%3a%2f%2fy%2f%3e+%3chttp%3a%2f%2fz%2f%3e+.+%7d%0d%0a</p>
<p>
But then gets back the 501 from the Sesame server:</p>
<p>
</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
HTTP/1.1 501 Not Implemented</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Server: Apache-Coyote/1.1</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Content-Type: text/html;charset=utf-8</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Content-Length: 2216</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Date: Tue, 15 Jan 2013 10:46:06 GMT</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
Connection: close</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; min-height: 9px; ">
</p>
<p style="margin: 0px; font-size: 8.5px; font-family: 'Lucida Console'; ">
<html><head><title>Apache Tomcat/7.0.26 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 501 - Method update=PREFIX+rdf%3a+%3chttp%3a%2f%2fwww.w3.org%2f1999%2f02%2f22-rdf-syntax-ns%23%3e%0d%0aPREFIX+rdfs%3a+%3chttp%3a%2f%2fwww.w3.org%2f2000%2f01%2frdf-schema%23%3e%0d%0aPREFIX+xsd%3a+%3chttp%3a%2f%2fwww.w3.org%2f2001%2fXMLSchema%23%3e%0d%0aINSERT+DATA%0d%0a%7b+%3chttp%3a%2f%2fx%2f%3e+%3chttp%3a%2f%2fy%2f%3e+%3chttp%3a%2f%2fz%2f%3e+.+%7d%0d%0aPOST is not is not implemented by this servlet for this URI</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Method update=PREFIX+rdf%3a+%3chttp%3a%2f%2fwww.w3.org%2f1999%2f02%2f22-rdf-syntax-ns%23%3e%0d%0aPREFIX+rdfs%3a+%3chttp%3a%2f%2fwww.w3.org%2f2000%2f01%2frdf-schema%23%3e%0d%0aPREFIX+xsd%3a+%3chttp%3a%2f%2fwww.w3.org%2f2001%2fXMLSchema%23%3e%0d%0aINSERT+DATA%0d%0a%7b+%3chttp%3a%2f%2fx%2f%3e+%3chttp%3a%2f%2fy%2f%3e+%3chttp%3a%2f%2fz%2f%3e+.+%7d%0d%0aPOST is not is not implemented by this servlet for this URI</u></p><p><b>description</b> <u>The server does not support the functionality needed to fulfill this request (Method update=PREFIX+rdf%3a+%3chttp%3a%2f%2fwww.w3.org%2f1999%2f02%2f22-rdf-syntax-ns%23%3e%0d%0aPREFIX+rdfs%3a+%3chttp%3a%2f%2fwww.w3.org%2f2000%2f01%2frdf-schema%23%3e%0d%0aPREFIX+xsd%3a+%3chttp%3a%2f%2fwww.w3.org%2f2001%2fXMLSchema%23%3e%0d%0aINSERT+DATA%0d%0a%7b+%3chttp%3a%2f%2fx%2f%3e+%3chttp%3a%2f%2fy%2f%3e+%3chttp%3a%2f%2fz%2f%3e+.+%7d%0d%0aPOST is not is not implemented by this servlet for this URI).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.26</h3></body></html></p>
<p>
Your analysis is correct that Sesame/Tomcat is misinterpreting the HTTP method on the second request somehow which I suspect is a problem in the servlets that Sesame uses to handle requests not in Tomcat itself.</p>
<p>
</p>
<p>
I will continue to look into this and possibly ping the Sesame developers to see what they make of this.</p>
<p>
</p>
<p>
By the way adding PreAuthenticate does not make a difference because that only causes .Net to cache the credentials after a successful authentication and send them for subsequent requests, it does not cause it to send the credentials from the very first request - see <a href="http://www.west-wind.com/weblog/posts/2010/Feb/18/NET-WebRequestPreAuthenticate-not-quite-what-it-sounds-like">http://www.west-wind.com/weblog/posts/2010/Feb/18/NET-WebRequestPreAuthenticate-not-quite-what-it-sounds-like</a></p>
<p>
</p>
<p>
</p>
<p>
</p>
<p>
</p>
<p>
</p>
<p>
</p>
<p>
</p>
<p>
</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>
|
|
From: <tr...@do...> - 2013-01-15 10:10:35
|
<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-15 10:09 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Having now reproduced this myself it looks much more like what you described and I think I now agree with your assesment,</p>
<p>
This seems very strange that Tomcat should behave this way, it almost looks like some sort of bug with Tomcat. I will get WireShark hooked up and see exactly what goes on.</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>
|
|
From: <tr...@do...> - 2013-01-14 18:56:12
|
<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-14 06:55 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2">p.s. It (dotNetRDF) worked fine before without authentication turned on.
We've been following this cookbook to enable HTTP basic authentication for the sesame endpoint:
http://rivuli-development.com/further-reading/sesame-cookbook/basic-security-with-http-authentication/</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>
|
|
From: <tr...@do...> - 2013-01-14 18:50:38
|
<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-14 06:49 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I will try recompiliing with the change to set request.PreAuthenticate = true and see if that fixes it. 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>
|
|
From: <tr...@do...> - 2013-01-14 18:47:32
|
<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-14 06:46 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2">Actually I'm pretty sure this is the problem. Looking at the dotNetRDF sesame connector code I believe what is happening is that the HTTPWebRequest is delivering the full POST (header + body) expecting it to go through, but Tomcat is rejecting it right after the initial header of the POST completes (thus 401 response) since no credentials are in the header.
I believe the POST header must not contain/specify the size of the body, so Tomcat has no choice but to go on and process the remaining body of the initial POST as a second HTTP request since this is HTTP/1.1 and the socket has been left open (unlike HTTP/1.0).
This fails (Response code 501) because the body of the POST by itself (without a header) is no longer HTTP protocol. If it were, then the log entry would be:
198.36.94.34 - - [09/Jan/2013:22:04:51 +0000] POST "update=PREFIX+rdf%3a+%3chttp%3a%2f....
Not
198.36.94.34 - - [09/Jan/2013:22:04:51 +0000] "update=PREFIX+rdf%3a+%3chttp%3a%2f...
Make sense?
I can try setting up Wireshark to get a snapshot of the exact full POST request to verify this is the case.</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>
|
|
From: <tr...@do...> - 2013-01-14 18:36:32
|
<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-14 06:35 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Just did a quick sanity check and confirmed that updates did work (with no HTTP authentication involved) on the most recent version of Sesame I have installed on my laptop (2.6.8) and it works. As far as I know Sesame have not changed how they do updates in any of the more recent releases so I still think this sounds like a Sesame/OWLIM issue</p>
<p>
</p>
<p>
Have you had chance to try running with a version of dotNetRDF modified to set PreAuthenticate to see if that actually makes any difference to the behaviour?</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>
|
|
From: <tr...@do...> - 2013-01-14 18:11:36
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Use PreAuthenticate for all HTTP operations</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Related issue changed from "" to "Added"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=302" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=302</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>
|
|
From: <tr...@do...> - 2013-01-14 18:11:23
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Use PreAuthenticate for all HTTP operations</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>Milestone:</b></td>
<td>0.9.0 RC 4</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Storage</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>High</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Improvement</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
This change was proposed by Daeron in CORE-301 as a bug fix, as discussed there we don't believe that PreAuthenticate is the cause of that particular bug but we do agree that we should be using PreAuthenticate since it will ultimately reduce round trips for our HTTP communications.</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=302" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=302</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>
|
|
From: <tr...@do...> - 2013-01-14 18:09:00
|
<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-14 06:08 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I think you have mis-read the logs here, enabling PreAuthenticate is likely a good idea that will reduce round trips to the server as it removes the need to HTTP authenticate on every request so we will do this but this looks not to be your actual problem.</p>
<p>
You get a 401 first which is the server telling us you need to include credentials but then the subsequent request which appears to be properly accepted (since the full request is detailed) yet your server is producing 501 Not Implemented in response to this. This is a slightly strange error to be produced and suggests that possibly the version of Sesame/OWLIM you are using does not support updates or at least not in the way dotNetRDF is attempting to make them. Or this may be the side effect of whatever HTTP security mechanism you are using.</p>
<p>
That looks like your Tomcat log, does the OWLIM/Sesame logs contain any more useful information about what is going wrong?</p>
<p>
You can have dotNetRDF produce debug traces of HTTP operations to the console by setting the global static Options.HttpDebugging which prints only the request and response headers. You can dump full responses by also enabling Options.HttpFullDebugging though this does consume the response and make it unusable elsewhere which tends to lead to various other errors as a by-product.</p>
<p>
If you can try enabling these and seeing what error message if any your server is sending back alongside that 501 and provide that information here this would be very helpful in determining where the actual problem lies.</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>
|
|
From: <tr...@do...> - 2013-01-14 17:03:34
|
<p>The following issue has been added to a project that you are monitoring.</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>Milestone:</b></td>
<td>none</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>none</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Critical</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
We have an OWLIM repository running as a sesame endpoint deployed to Tomcat. After securing all forms of access (GET, POST, PUT, DELETE) to the repositories path of the endpoint we began seeing the following in our logs and noticed that any SPARQL update was failing:</p>
<p>
198.36.94.34 - - [09/Jan/2013:22:04:51 +0000] "POST /openrdf-sesame/repositories/31FD2E58-0F06-4D16-A663-D9D142CBB66D/statements HTTP/1.1" <strong>401</strong> 951<br />
198.36.94.34 - - [09/Jan/2013:22:04:51 +0000] "update=PREFIX+rdf%3a+%3chttp%3a%2f%2fwww.w3.org%2f1999%2f02%2f22-rdf-syntax-ns%23%3e%0d%0aPREFIX+%3a+%3chttp%3a%2f%2fwww.jci.com%2fPanoptixBaseOntology%23%3e%0d%0aPREFIX+rdfs%3a%3chttp%3a%2f%2fwww.w3.org%2f2000%2f01%2frdf-schema%23%3e%0d%0aPREFIX+owl%3a%3chttp%3a%2f%2fwww.w3.org%2f2002%2f07%2fowl%23%3e%0d%0aINSERT+DATA%0d%0a%7b%0d%0a%3chttp%3a%2f%2fwww.jci.com%2fPanoptixBaseOntology%234569752E-4DAB-4CC3-A979-D6502D1A3004%3e+rdf%3atype+owl%3aNamedIndividual+.%0d%0a%3chttp%3a%2f%2fwww.jci.com%2fPanoptixBaseOntology%234569752E-4DAB-4CC3-A979-D6502D1A3004%3e+rdf%3atype+%3aPoint+.%0d%0a%3chttp%3a%2f%2fwww.jci.com%2fPanoptixBaseOntology%234569752E-4DAB-4CC3-A979-D6502D1A3004%3e+%3aname+%22Daeron%22+.%0d%0a%3chttp%3a%2f%2fwww.jci.com%2fPanoptixBaseOntology%234569752E-4DAB-4CC3-A979-D6502D1A3004%3e+%3adescription+%22Daeron%22+.%0d%0a%3chttp%3a%2f%2fwww.jci.com%2fPanoptixBaseOntology%234569752E-4DAB-4CC3-A979-D6502D1A3004%3e+%3apointGuid+%2220000000-0000-0000-0000-000000000000%22+.%0d%0a%7dPOST /openrdf-sesame/repositories/31FD2E58-0F06-4D16-A663-D9D142CBB66D/statements HTTP/1.1" <strong>501</strong> 3110</p>
<p>
Looking into the source code for the BaseSesameHttpProtocolConnector I noticed that in HttpWebRequest CreateRequest(....) you are setting the NetworkCredential on the request when one is provided:</p>
<p>
if (this._hasCredentials)<br />
{<br />
NetworkCredential credentials = new NetworkCredential(this._username, this._pwd);<br />
request.Credentials = credentials; <br />
}</p>
<p>
However, you failed to set request.PreAuthenticate = true; This means that in some cases the credential will simply not be sent which appears to be what happened here - thus the 401 response and garbage/501 on the post contents which got processed by Tomcat as a second HTTP Request. More information here:</p>
<p>
http://stackoverflow.com/questions/1702426/httpwebrequest-not-passing-credentials</p>
<p>
http://msdn.microsoft.com/en-us/library/system.net.httpwebrequest.preauthenticate.aspx</p>
<p>
Please fix this by setting request.PreAuthenticate = true.</p>
<p>
</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>
|
|
From: Tomasz P. <tom...@gm...> - 2013-01-09 14:00:19
|
Rob, Integration tests is one thing and continuous testing/integration is something else. I know it's not ideal to be able to run TeamCity with an incomplete test suite but it is better then have none at all. I have two ideas though: 1. Is it possible to bootstrap the triple stores in TeamCity and start locally there? I know some are Linux-only but maybe we could execute some tests... 2. Maybe you could set up the the triple stores hosted somewhere for the TeamCity to reach remotely? This could be a security issue though and tests' performance will degrade. And regarding licensing. TeamCity at codebetter is not exactly JetBrains. They don't have any restrictions. If the project is open source you can ask them to host your integration environment. What they want in return is a banner linking to JetBrains. And EC2 could be costly. I have recently learned my lesson about Amazon :(. Oh, and there is a free TeamCity version with a limit on agents. That should be enough for one project. Tom On Wed, Jan 9, 2013 at 1:20 PM, Rob Vesse <rv...@do...> wrote: > I have an open issue for setting up some form of CI server but I haven't > had the time to do anything on this due to work and personal constraints. > See CORE-276 [1], I would prefer to go with some sort of self hosted > solution (likely Jenkins on EC2) as otherwise we won't be able to > regularly test third party triple store integration. > > Alternative suggestions are welcome, my problem with JetBrains is that > their definition of OSS requires a sufficiently active community and I'm > not sure that us two and a few others discussing back and forth would > count as sufficiently active > > Rob > > [1] http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=276 > > On 1/5/13 6:05 PM, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >>Hi Everyone >> >>Some time ago we've been discussing setting up TeamCity. I >>wholeheartedly support this initiative and regret it's been dropped >>previously. I am getting a lot of failed tests when I run them locally >>(and I don't mean the remote/store tests). I find this a clear sign >>that we definitely need a continous integration environment to keep >>quality high. >> >>Now, that I have been using TeamCity at my current project for some >>time I feel like I'm ready to help with setting it up. Have you guys >>heard about teamcity.codebetter.com? Or maybe host a project there? >>It's a TeamCity server free for OSS projects. There is a form, which >>needs to be filled in. I have filed a request with my R2RML project >>but there is still no answer, so I'm not sure how long the wait is... >> >>Anyway, what do you think? Any opinions? >> >>Regards, >>Tom >> >>-------------------------------------------------------------------------- >>---- >>Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, >>MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current >>with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft >>MVPs and experts. SALE $99.99 this month only -- learn more at: >>http://p.sf.net/sfu/learnmore_122912 >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery > and much more. Keep your Java skills current with LearnJavaNow - > 200+ hours of step-by-step video tutorials by Java experts. > SALE $49.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122612 > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
48 messages has been excluded from this view by a project administrator.
