I did a test with the version 1.0.20-beta with jira 5.0.2.
Our access to internet is secured via a proxy. The security rules have been re-enforced recently.
Now each time that I use the jira instance, I have a basic authentication screen to enter my credentials.
I used Live HTTP headers to see what is requested and the result is:
https://jira.atlassian.com/s/en_UK9dpx5o/713/4/1.0.20-beta/_/download/batch/com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector/com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector.js?collectorId=d3de7fb5
GET /s/en_UK9dpx5o/713/4/1.0.20-beta/_/download/batch/com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector/com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector.js?collectorId=d3de7fb5 HTTP/1.1
Host: jira.atlassian.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.3) Gecko/20100101 Firefox/10.0.3
Accept: */*
Accept-Language: fr,en;q=0.7,de;q=0.3
Accept-Encoding: gzip, deflate
DNT: 1
Connection: keep-alive
Referer: http://myserver/secure/AdminSummary.jspa
Proxy-Authorization: Basic XXXXXX
HTTP/1.1 200 OK
Date: Fri, 01 Jun 2012 09:48:56 GMT
Server: Apache-Coyote/1.1
X-AREQUESTID: 288x1924711x3
Expires: Sat, 01 Jun 2013 09:48:56 GMT
Cache-Control: max-age=31536000, public
X-AUSERNAME: anonymous
Last-Modified: Mon, 28 May 2012 12:35:03 GMT
Etag: "1338208503000"
Content-Type: application/x-javascript;charset=UTF-8
Vary: Accept-Encoding
Content-Encoding: gzip
X-Robots-Tag: noindex, noarchive
Connection: close
Transfer-Encoding: chunked
Next to that, I have uninstalled the plugin, restarted jira and the call to this resource is still requested...
What's happening?
https://bitbucket.org/atlassian/jira-issue-collector-plugin/issue/28/jira-issue-collector-is-doing-an-external has been created
Bruno
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.