[JIRA] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials

Tue, 09 Sep 2014 07:00:56 -0700

Daniel Beck commented on Improvement JENKINS-6610

And if the RSS client doesn't support this method? It's obvious people won't use curl to get their RSS. ... My guess is to make it compatible or add a &netrc=<value> for the API token.

To clarify, this is basic HTTP auth under the hood. --netrc just reads the username and password from a file rather than expecting username and password as parameters on the command line. I tested this just to be absolutely sure, 

curl -u danielbeck:my_API_token http://jenkins/rssAll
works like a charm as well on an instance (Jenkins 1.565.2) without anon read access.



Hence my assertion that, if your RSS (HTTP) client cannot do basic HTTP authentication, that's not a problem of Jenkins.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to