[jbosstools-issues] [JBoss JIRA] (JBIDE-17453) Error while validating credentials in Download Runtime dialog

David Hladky (JIRA) issues at jboss.org
Tue Jun 3 04:31:16 EDT 2014


    [ https://issues.jboss.org/browse/JBIDE-17453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972714#comment-12972714 ] 

David Hladky commented on JBIDE-17453:
--------------------------------------

I investigated the code and the problem here is the lack of the documentation. The service now returns 200 and valid "current step" information or 403 if the user downloading the artifact does not have the right to download the file (i.e. he did not sign the terms and conditions), but does not request supply application/xml or application/json content type header. 

>From my point of view it is a good behaviour, but wrong is the final step (302 = file started to be downloaded). It may appear it is OK on the first sight, but 302 might  be caused by an Apache server before the request reaches JBoss Downloader and Eclipse may consider it to be a response from JBoss Downloader with the dowloaded file . 

Rob, will you, please, contact me over IRC so we can discuss it a bit more?

> Error while validating credentials in Download Runtime dialog
> -------------------------------------------------------------
>
>                 Key: JBIDE-17453
>                 URL: https://issues.jboss.org/browse/JBIDE-17453
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: runtime-detection
>    Affects Versions: 4.2.0.Beta2
>            Reporter: Radoslav Rábara
>            Assignee: Rob Stryker
>            Priority: Blocker
>              Labels: respin-b
>             Fix For: 4.2.0.Beta2
>
>         Attachments: credentials validation error.jpg
>
>
> After validation of valid credentials, the following error message appears
> {code}
> "An error occured while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 200"
> {code}
> I was able to reproduce this issue only with one of mine jboss.org accounts.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)



More information about the jbosstools-issues mailing list