[jira] [Commented] (CONNECTORS-157) Some relative paths without leading / do not resolve properly

2011-08-18 Thread David Broadfoot (JIRA)

[ 
https://issues.apache.org/jira/browse/CONNECTORS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13087000#comment-13087000
 ] 

David Broadfoot commented on CONNECTORS-157:


Works like a charm. Many thanks!

 Some relative paths without leading / do not resolve properly
 -

 Key: CONNECTORS-157
 URL: https://issues.apache.org/jira/browse/CONNECTORS-157
 Project: ManifoldCF
  Issue Type: Bug
  Components: RSS connector, Web connector
Affects Versions: ManifoldCF 0.1
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.2, ManifoldCF 0.3


 If a document has a URL which is just the domain, e.g. http://foo.com;, the 
 java.net.URI class fails to resolve URLs in that document which have no 
 starting /, e.g. document.pdf.  The resolved URI has no path part, e.g. 
 http://foo.comdocument.pdf;.
 Another similar case is the following:
 http://foo.com/bar/xyz.asmx?q=hello;
 ... with a relative URL of q=there
 ... produces: http://foo.com/bar/?q=there;, incorrectly losing the last part 
 of the path.
 This is apparently a bug, but we need to find a way to work around it 
 properly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (CONNECTORS-157) Some relative paths without leading / do not resolve properly

2011-08-16 Thread Karl Wright (JIRA)

[ 
https://issues.apache.org/jira/browse/CONNECTORS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13086059#comment-13086059
 ] 

Karl Wright commented on CONNECTORS-157:


r1158476 to port the same fixes to the RSS connector.


 Some relative paths without leading / do not resolve properly
 -

 Key: CONNECTORS-157
 URL: https://issues.apache.org/jira/browse/CONNECTORS-157
 Project: ManifoldCF
  Issue Type: Bug
  Components: RSS connector, Web connector
Affects Versions: ManifoldCF 0.1
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.2, ManifoldCF 0.3


 If a document has a URL which is just the domain, e.g. http://foo.com;, the 
 java.net.URI class fails to resolve URLs in that document which have no 
 starting /, e.g. document.pdf.  The resolved URI has no path part, e.g. 
 http://foo.comdocument.pdf;.
 Another similar case is the following:
 http://foo.com/bar/xyz.asmx?q=hello;
 ... with a relative URL of q=there
 ... produces: http://foo.com/bar/?q=there;, incorrectly losing the last part 
 of the path.
 This is apparently a bug, but we need to find a way to work around it 
 properly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (CONNECTORS-157) Some relative paths without leading / do not resolve properly

2011-08-16 Thread Karl Wright (JIRA)

[ 
https://issues.apache.org/jira/browse/CONNECTORS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13086062#comment-13086062
 ] 

Karl Wright commented on CONNECTORS-157:


r1158480 to add similar tests to the RSS connector.


 Some relative paths without leading / do not resolve properly
 -

 Key: CONNECTORS-157
 URL: https://issues.apache.org/jira/browse/CONNECTORS-157
 Project: ManifoldCF
  Issue Type: Bug
  Components: RSS connector, Web connector
Affects Versions: ManifoldCF 0.1
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 0.2, ManifoldCF 0.3


 If a document has a URL which is just the domain, e.g. http://foo.com;, the 
 java.net.URI class fails to resolve URLs in that document which have no 
 starting /, e.g. document.pdf.  The resolved URI has no path part, e.g. 
 http://foo.comdocument.pdf;.
 Another similar case is the following:
 http://foo.com/bar/xyz.asmx?q=hello;
 ... with a relative URL of q=there
 ... produces: http://foo.com/bar/?q=there;, incorrectly losing the last part 
 of the path.
 This is apparently a bug, but we need to find a way to work around it 
 properly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira