You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2006/12/05 09:43:21 UTC
[jira] Created: (HTTPCLIENT-611) broken RFC links
broken RFC links
----------------
Key: HTTPCLIENT-611
URL: http://issues.apache.org/jira/browse/HTTPCLIENT-611
Project: HttpComponents HttpClient
Issue Type: Task
Components: Documentation
Reporter: Julian Reschke
Priority: Trivial
Some of the RFC links in the web site are broken, for instance RFC2616 links to "http://jakarta.apache.org/commons/httpclient/methods/rfc2616.html", which gives a 404.
I recommend to always use http://tools.ietf.org/html/rfcNNNN, which also gives the ability to directly link to an RFC section (Example: <http://tools.ietf.org/html/rfc2616#section-5>).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org
[jira] Commented: (HTTPCLIENT-611) broken RFC links
Posted by "Ortwin Glück (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HTTPCLIENT-611?page=comments#action_12455557 ]
Ortwin Glück commented on HTTPCLIENT-611:
-----------------------------------------
Julian,
Plaese post the URLs of the page that contains the broken links.
Thanks
Ortwin
> broken RFC links
> ----------------
>
> Key: HTTPCLIENT-611
> URL: http://issues.apache.org/jira/browse/HTTPCLIENT-611
> Project: HttpComponents HttpClient
> Issue Type: Task
> Components: Documentation
> Reporter: Julian Reschke
> Priority: Trivial
> Fix For: 3.1 Final
>
>
> Some of the RFC links in the web site are broken, for instance RFC2616 links to "http://jakarta.apache.org/commons/httpclient/methods/rfc2616.html", which gives a 404.
> I recommend to always use http://tools.ietf.org/html/rfcNNNN, which also gives the ability to directly link to an RFC section (Example: <http://tools.ietf.org/html/rfc2616#section-5>).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org
[jira] Commented: (HTTPCLIENT-611) broken RFC links
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HTTPCLIENT-611?page=comments#action_12455559 ]
Julian Reschke commented on HTTPCLIENT-611:
-------------------------------------------
For instance: http://jakarta.apache.org/commons/httpclient/features.html, but I think I saw similar bugs elsewhere as well. A task for "grep"?
> broken RFC links
> ----------------
>
> Key: HTTPCLIENT-611
> URL: http://issues.apache.org/jira/browse/HTTPCLIENT-611
> Project: HttpComponents HttpClient
> Issue Type: Task
> Components: Documentation
> Reporter: Julian Reschke
> Priority: Trivial
> Fix For: 3.1 Final
>
>
> Some of the RFC links in the web site are broken, for instance RFC2616 links to "http://jakarta.apache.org/commons/httpclient/methods/rfc2616.html", which gives a 404.
> I recommend to always use http://tools.ietf.org/html/rfcNNNN, which also gives the ability to directly link to an RFC section (Example: <http://tools.ietf.org/html/rfc2616#section-5>).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org
[jira] Updated: (HTTPCLIENT-611) broken RFC links
Posted by "Oleg Kalnichevski (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HTTPCLIENT-611?page=all ]
Oleg Kalnichevski updated HTTPCLIENT-611:
-----------------------------------------
Fix Version/s: 3.1 Final
> broken RFC links
> ----------------
>
> Key: HTTPCLIENT-611
> URL: http://issues.apache.org/jira/browse/HTTPCLIENT-611
> Project: HttpComponents HttpClient
> Issue Type: Task
> Components: Documentation
> Reporter: Julian Reschke
> Priority: Trivial
> Fix For: 3.1 Final
>
>
> Some of the RFC links in the web site are broken, for instance RFC2616 links to "http://jakarta.apache.org/commons/httpclient/methods/rfc2616.html", which gives a 404.
> I recommend to always use http://tools.ietf.org/html/rfcNNNN, which also gives the ability to directly link to an RFC section (Example: <http://tools.ietf.org/html/rfc2616#section-5>).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org
[jira] Resolved: (HTTPCLIENT-611) broken RFC links
Posted by "Ortwin Glück (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HTTPCLIENT-611?page=all ]
Ortwin Glück resolved HTTPCLIENT-611.
-------------------------------------
Fix Version/s: (was: 3.1 Final)
Resolution: Invalid
> broken RFC links
> ----------------
>
> Key: HTTPCLIENT-611
> URL: http://issues.apache.org/jira/browse/HTTPCLIENT-611
> Project: HttpComponents HttpClient
> Issue Type: Task
> Components: Documentation
> Reporter: Julian Reschke
> Priority: Trivial
>
> Some of the RFC links in the web site are broken, for instance RFC2616 links to "http://jakarta.apache.org/commons/httpclient/methods/rfc2616.html", which gives a 404.
> I recommend to always use http://tools.ietf.org/html/rfcNNNN, which also gives the ability to directly link to an RFC section (Example: <http://tools.ietf.org/html/rfc2616#section-5>).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org
[jira] Commented: (HTTPCLIENT-611) broken RFC links
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HTTPCLIENT-611?page=comments#action_12455598 ]
Julian Reschke commented on HTTPCLIENT-611:
-------------------------------------------
Apologies. I was victim of a misbehaving Greasemonkey script (yes, written by myself).
> broken RFC links
> ----------------
>
> Key: HTTPCLIENT-611
> URL: http://issues.apache.org/jira/browse/HTTPCLIENT-611
> Project: HttpComponents HttpClient
> Issue Type: Task
> Components: Documentation
> Reporter: Julian Reschke
> Priority: Trivial
> Fix For: 3.1 Final
>
>
> Some of the RFC links in the web site are broken, for instance RFC2616 links to "http://jakarta.apache.org/commons/httpclient/methods/rfc2616.html", which gives a 404.
> I recommend to always use http://tools.ietf.org/html/rfcNNNN, which also gives the ability to directly link to an RFC section (Example: <http://tools.ietf.org/html/rfc2616#section-5>).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org
[jira] Commented: (HTTPCLIENT-611) broken RFC links
Posted by "Ortwin Glück (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HTTPCLIENT-611?page=comments#action_12455560 ]
Ortwin Glück commented on HTTPCLIENT-611:
-----------------------------------------
Julian,
I might be missing something, but I don't see any invalid RFC link on that page. They all look like:
<a href="http://www.ietf.org/rfc/rfc2616.txt" class="externalLink" title="External Link">RFC2616</a>
Hypertext Transfer Protocol -- HTTP/1.1
PS: Maven actually does link checking when generating the site.
> broken RFC links
> ----------------
>
> Key: HTTPCLIENT-611
> URL: http://issues.apache.org/jira/browse/HTTPCLIENT-611
> Project: HttpComponents HttpClient
> Issue Type: Task
> Components: Documentation
> Reporter: Julian Reschke
> Priority: Trivial
> Fix For: 3.1 Final
>
>
> Some of the RFC links in the web site are broken, for instance RFC2616 links to "http://jakarta.apache.org/commons/httpclient/methods/rfc2616.html", which gives a 404.
> I recommend to always use http://tools.ietf.org/html/rfcNNNN, which also gives the ability to directly link to an RFC section (Example: <http://tools.ietf.org/html/rfc2616#section-5>).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org