[JBoss JIRA] (JBIDE-17895) Consume wtp patch build (update to Luna SR1)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17895?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-17895:
----------------------------------------
Please not that even if we do update TP to Luna SR1, people who only get Luna R and install JBT 4.2.0 will still keep there old version of WTP with the various bugs mentioned.
If you want to force them to use the newer version, then you need to make the necessary changes in dependency managment (MANIFEST.MF, feature.xml), but I'm not sure we want to force people to update, do we?
For JBDS, we'll include Luna SR1 so the patches should be in.
> Consume wtp patch build (update to Luna SR1)
> --------------------------------------------
>
> Key: JBIDE-17895
> URL: https://issues.jboss.org/browse/JBIDE-17895
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, server, target-platform, upstream
> Affects Versions: 4.2.0.Beta3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=437351
> The patch build currently lives at http://build.eclipse.org/webtools/committers/patches-R3.6.0-P/20140701141...
> However, I'm not sure that's the ultimate location for the future.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-14001) First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14001?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-14001:
-------------------------------------
Linking related issue
> First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14001
> URL: https://issues.jboss.org/browse/JBIDE-14001
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.0.1.Final
> Environment: Windows 7
> Reporter: David Stephan
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
>
> After Marking a jar as deployable and deploying to EAP server, the jar is deployed correctly.
> Then, after restarting JBDS, then restarting the app server from within JBDS, the deployed jar is deleted.
> After restarting the server again, the jar is deployed, and subsequent restarts don't remove the jar.
> Possibly related, when you first mark the jar as deployable and deploy to a server, the context menu item changes to "Unmark as Deployable." After a restart of JBDS, this context menu item is back to "Mark as Deployable".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-14001) First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14001?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-14001:
--------------------------------
Fix Version/s: 4.2.0.CR2
(was: 4.2.x)
> First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14001
> URL: https://issues.jboss.org/browse/JBIDE-14001
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.0.1.Final
> Environment: Windows 7
> Reporter: David Stephan
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
>
> After Marking a jar as deployable and deploying to EAP server, the jar is deployed correctly.
> Then, after restarting JBDS, then restarting the app server from within JBDS, the deployed jar is deleted.
> After restarting the server again, the jar is deployed, and subsequent restarts don't remove the jar.
> Possibly related, when you first mark the jar as deployable and deploy to a server, the context menu item changes to "Unmark as Deployable." After a restart of JBDS, this context menu item is back to "Mark as Deployable".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18429) Forge New Project wizard - field names should have the same case
by George Gastaldi (JIRA)
George Gastaldi created JBIDE-18429:
---------------------------------------
Summary: Forge New Project wizard - field names should have the same case
Key: JBIDE-18429
URL: https://issues.jboss.org/browse/JBIDE-18429
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.2.0.CR1
Reporter: George Gastaldi
Forge 2 New Project wizard field names should have consistent sentence case - see Guideline 1.6 http://wiki.eclipse.org/User_Interface_Guidelines#Capitalization.
* Ctrl+4 + New Project
* Final Name > Final name
* Project Type > Project type
* Build System > Build system
For 'From Archetype' window:
* Archetype Repository > Archetype repository << would it be clearer if were 'Archetype repository URL'?
* Enter a maven archetype coordinate > Enter a Maven archetype coordinate
For 'From Archetype Catalog' window:
* Choose a maven archetype for your project > Choose a Maven archetype for your project
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18415) Forge New Project wizard - no Archetype catalogues listed
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18415?page=com.atlassian.jira.plugi... ]
George Gastaldi commented on JBIDE-18415:
-----------------------------------------
We can pre-populate with the archetypes in the preferences page. For the link in the wizard, that is not possible at the moment.
> Forge New Project wizard - no Archetype catalogues listed
> ---------------------------------------------------------
>
> Key: JBIDE-18415
> URL: https://issues.jboss.org/browse/JBIDE-18415
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR1
> Reporter: Michelle Murray
>
> Forge 2 New Project wizard lists no catalogs for 'From Archetype Catalog' project option.
> * Ctrl+4
> * New Project
> * Project name: blah
> * Project type: From Archetype Catalog >> no options for Catalog or Archetype
> Could this list be populated by Preferences > Maven > Archetypes > Archetype Catalog Table? And have a link in the wizard to this preference page for users to quickly add another catalog? (Like the OpenShift wizard has a link to SSH Preferences for adding private key to IDE in middle of wizard.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18428) Connection wizard: get "Unknown error" instead of "Authentication error" when using bad credentials (WATCHER)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18428?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18428:
-------------------------------------
Description:
The issues is that OpenShift Online responds with *500 Internal Server Error* when invalid credentials are being used (where *401 Unauthorized* is expect)
{code}
curl -v --user adietish@redhat.com:bogus https://openshift.redhat.com/broker/rest/user* Adding handle: conn: 0xaa8a80
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0xaa8a80) send_pipe: 1, recv_pipe: 0
* About to connect() to openshift.redhat.com port 443 (#0)
* Trying 50.19.249.93...
* Connected to openshift.redhat.com (50.19.249.93) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_RSA_WITH_AES_128_CBC_SHA
* Server certificate:
* subject: CN=openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US
* start date: Jul 23 00:00:00 2014 GMT
* expire date: Jul 27 12:00:00 2017 GMT
* common name: openshift.redhat.com
* issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
* Server auth using Basic with user 'adietish(a)redhat.com'
> GET /broker/rest/user HTTP/1.1
> Authorization: Basic YWRpZXRpc2hAcmVkaGF0LmNvbTpib2d1cw==
> User-Agent: curl/7.32.0
> Host: openshift.redhat.com
> Accept: */*
>
< HTTP/1.1 500
< Cache-Control: no-cache, private
< Content-Type: application/json; charset=utf-8
< Date: Wed, 24 Sep 2014 10:18:21 GMT
< ProxyTime: D=374659
* Server Apache/2.2.15 (Red Hat) is not blacklisted
< Server: Apache/2.2.15 (Red Hat)
< Status: 500
< Strict-Transport-Security: max-age=15768000, includeSubDomains
< Vary: Accept-Encoding,User-Agent
< X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21
< X-Rack-Cache: miss
< X-Request-Id: b25500e832d6bbebb1bc7eee5e3175b4
< X-Runtime: 0.367919
< X-UA-Compatible: IE=Edge,chrome=1
< Content-Length: 376
< Connection: keep-alive
<
* Connection #0 to host openshift.redhat.com left intact
{"api_version":1.7,"data":null,"messages":[{"exit_code":1,"field":null,"index":null,"severity":"error","text":"Unable to authenticate the user. Please try again and contact support if the issue persists. \nReference ID: b25500e832d6bbebb1bc7eee5e3175b4"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4,1.5,1.6,1.7],"type":null,"version":"1.7"}
{code}
stg.openshift.redaht.com is responding with the correct 401:
{code}
[adietish@localhost openshift-java-client]$ curl -v --proxy https://file.rdu.redhat.com:3128 --user adietish@redhat.com:bogus https://stg.openshift.redhat.com/broker/rest/user
* Adding handle: conn: 0x178dae0
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x178dae0) send_pipe: 1, recv_pipe: 0
* About to connect() to proxy file.rdu.redhat.com port 3128 (#0)
* Trying 10.11.5.7...
* Connected to file.rdu.redhat.com (10.11.5.7) port 3128 (#0)
* Establish HTTP proxy tunnel to stg.openshift.redhat.com:443
* Server auth using Basic with user 'adietish(a)redhat.com'
> CONNECT stg.openshift.redhat.com:443 HTTP/1.1
> Host: stg.openshift.redhat.com:443
> User-Agent: curl/7.32.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.0 200 Connection established
<
* Proxy replied OK to CONNECT request
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA
* Server certificate:
* subject: CN=stg.openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US
* start date: Apr 30 00:00:00 2014 GMT
* expire date: May 04 12:00:00 2016 GMT
* common name: stg.openshift.redhat.com
* issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
* Server auth using Basic with user 'adietish(a)redhat.com'
> GET /broker/rest/user HTTP/1.1
> Authorization: Basic YWRpZXRpc2hAcmVkaGF0LmNvbTpib2d1cw==
> User-Agent: curl/7.32.0
> Host: stg.openshift.redhat.com
> Accept: */*
>
< HTTP/1.1 401
< Date: Wed, 24 Sep 2014 10:19:22 GMT
* Server Apache/2.2.15 (Red Hat) is not blacklisted
< Server: Apache/2.2.15 (Red Hat)
< X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21
* Authentication problem. Ignoring this.
< WWW-Authenticate: Basic realm="Application"
< X-UA-Compatible: IE=Edge,chrome=1
< Cache-Control: no-cache, private
< X-Request-Id: 5217138e18f0e036b1880d006e4c3cb6
< X-Runtime: 0.569233
< X-Rack-Cache: miss
< Status: 401
< Content-Length: 27
< Content-Type: text/html; charset=utf-8
< Vary: Accept-Encoding,User-Agent
< Strict-Transport-Security: max-age=15768000, includeSubDomains
< ProxyTime: D=574882
<
HTTP Basic: Access denied.
* Connection #0 to host file.rdu.redhat.com left intact
{code}
was:
The issues is that OpenShift Online responds with *500 Internal Server Error" when invalid credentials are being used (where *401 Unauthorized* is expect)
{code}
curl -v --user adietish@redhat.com:bogus https://openshift.redhat.com/broker/rest/user* Adding handle: conn: 0xaa8a80
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0xaa8a80) send_pipe: 1, recv_pipe: 0
* About to connect() to openshift.redhat.com port 443 (#0)
* Trying 50.19.249.93...
* Connected to openshift.redhat.com (50.19.249.93) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_RSA_WITH_AES_128_CBC_SHA
* Server certificate:
* subject: CN=openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US
* start date: Jul 23 00:00:00 2014 GMT
* expire date: Jul 27 12:00:00 2017 GMT
* common name: openshift.redhat.com
* issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
* Server auth using Basic with user 'adietish(a)redhat.com'
> GET /broker/rest/user HTTP/1.1
> Authorization: Basic YWRpZXRpc2hAcmVkaGF0LmNvbTpib2d1cw==
> User-Agent: curl/7.32.0
> Host: openshift.redhat.com
> Accept: */*
>
< HTTP/1.1 500
< Cache-Control: no-cache, private
< Content-Type: application/json; charset=utf-8
< Date: Wed, 24 Sep 2014 10:18:21 GMT
< ProxyTime: D=374659
* Server Apache/2.2.15 (Red Hat) is not blacklisted
< Server: Apache/2.2.15 (Red Hat)
< Status: 500
< Strict-Transport-Security: max-age=15768000, includeSubDomains
< Vary: Accept-Encoding,User-Agent
< X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21
< X-Rack-Cache: miss
< X-Request-Id: b25500e832d6bbebb1bc7eee5e3175b4
< X-Runtime: 0.367919
< X-UA-Compatible: IE=Edge,chrome=1
< Content-Length: 376
< Connection: keep-alive
<
* Connection #0 to host openshift.redhat.com left intact
{"api_version":1.7,"data":null,"messages":[{"exit_code":1,"field":null,"index":null,"severity":"error","text":"Unable to authenticate the user. Please try again and contact support if the issue persists. \nReference ID: b25500e832d6bbebb1bc7eee5e3175b4"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4,1.5,1.6,1.7],"type":null,"version":"1.7"}
{code}
stg.openshift.redaht.com is responding with the correct 401:
{code}
[adietish@localhost openshift-java-client]$ curl -v --proxy https://file.rdu.redhat.com:3128 --user adietish@redhat.com:bogus https://stg.openshift.redhat.com/broker/rest/user
* Adding handle: conn: 0x178dae0
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x178dae0) send_pipe: 1, recv_pipe: 0
* About to connect() to proxy file.rdu.redhat.com port 3128 (#0)
* Trying 10.11.5.7...
* Connected to file.rdu.redhat.com (10.11.5.7) port 3128 (#0)
* Establish HTTP proxy tunnel to stg.openshift.redhat.com:443
* Server auth using Basic with user 'adietish(a)redhat.com'
> CONNECT stg.openshift.redhat.com:443 HTTP/1.1
> Host: stg.openshift.redhat.com:443
> User-Agent: curl/7.32.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.0 200 Connection established
<
* Proxy replied OK to CONNECT request
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA
* Server certificate:
* subject: CN=stg.openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US
* start date: Apr 30 00:00:00 2014 GMT
* expire date: May 04 12:00:00 2016 GMT
* common name: stg.openshift.redhat.com
* issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
* Server auth using Basic with user 'adietish(a)redhat.com'
> GET /broker/rest/user HTTP/1.1
> Authorization: Basic YWRpZXRpc2hAcmVkaGF0LmNvbTpib2d1cw==
> User-Agent: curl/7.32.0
> Host: stg.openshift.redhat.com
> Accept: */*
>
< HTTP/1.1 401
< Date: Wed, 24 Sep 2014 10:19:22 GMT
* Server Apache/2.2.15 (Red Hat) is not blacklisted
< Server: Apache/2.2.15 (Red Hat)
< X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21
* Authentication problem. Ignoring this.
< WWW-Authenticate: Basic realm="Application"
< X-UA-Compatible: IE=Edge,chrome=1
< Cache-Control: no-cache, private
< X-Request-Id: 5217138e18f0e036b1880d006e4c3cb6
< X-Runtime: 0.569233
< X-Rack-Cache: miss
< Status: 401
< Content-Length: 27
< Content-Type: text/html; charset=utf-8
< Vary: Accept-Encoding,User-Agent
< Strict-Transport-Security: max-age=15768000, includeSubDomains
< ProxyTime: D=574882
<
HTTP Basic: Access denied.
* Connection #0 to host file.rdu.redhat.com left intact
{code}
> Connection wizard: get "Unknown error" instead of "Authentication error" when using bad credentials (WATCHER)
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18428
> URL: https://issues.jboss.org/browse/JBIDE-18428
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, upstream
> Fix For: 4.3.x
>
> Attachments: unknown-error.png
>
>
> The issues is that OpenShift Online responds with *500 Internal Server Error* when invalid credentials are being used (where *401 Unauthorized* is expect)
> {code}
> curl -v --user adietish@redhat.com:bogus https://openshift.redhat.com/broker/rest/user* Adding handle: conn: 0xaa8a80
> * Adding handle: send: 0
> * Adding handle: recv: 0
> * Curl_addHandleToPipeline: length: 1
> * - Conn 0 (0xaa8a80) send_pipe: 1, recv_pipe: 0
> * About to connect() to openshift.redhat.com port 443 (#0)
> * Trying 50.19.249.93...
> * Connected to openshift.redhat.com (50.19.249.93) port 443 (#0)
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> * CAfile: /etc/pki/tls/certs/ca-bundle.crt
> CApath: none
> * SSL connection using TLS_RSA_WITH_AES_128_CBC_SHA
> * Server certificate:
> * subject: CN=openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US
> * start date: Jul 23 00:00:00 2014 GMT
> * expire date: Jul 27 12:00:00 2017 GMT
> * common name: openshift.redhat.com
> * issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
> * Server auth using Basic with user 'adietish(a)redhat.com'
> > GET /broker/rest/user HTTP/1.1
> > Authorization: Basic YWRpZXRpc2hAcmVkaGF0LmNvbTpib2d1cw==
> > User-Agent: curl/7.32.0
> > Host: openshift.redhat.com
> > Accept: */*
> >
> < HTTP/1.1 500
> < Cache-Control: no-cache, private
> < Content-Type: application/json; charset=utf-8
> < Date: Wed, 24 Sep 2014 10:18:21 GMT
> < ProxyTime: D=374659
> * Server Apache/2.2.15 (Red Hat) is not blacklisted
> < Server: Apache/2.2.15 (Red Hat)
> < Status: 500
> < Strict-Transport-Security: max-age=15768000, includeSubDomains
> < Vary: Accept-Encoding,User-Agent
> < X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21
> < X-Rack-Cache: miss
> < X-Request-Id: b25500e832d6bbebb1bc7eee5e3175b4
> < X-Runtime: 0.367919
> < X-UA-Compatible: IE=Edge,chrome=1
> < Content-Length: 376
> < Connection: keep-alive
> <
> * Connection #0 to host openshift.redhat.com left intact
> {"api_version":1.7,"data":null,"messages":[{"exit_code":1,"field":null,"index":null,"severity":"error","text":"Unable to authenticate the user. Please try again and contact support if the issue persists. \nReference ID: b25500e832d6bbebb1bc7eee5e3175b4"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4,1.5,1.6,1.7],"type":null,"version":"1.7"}
> {code}
> stg.openshift.redaht.com is responding with the correct 401:
> {code}
> [adietish@localhost openshift-java-client]$ curl -v --proxy https://file.rdu.redhat.com:3128 --user adietish@redhat.com:bogus https://stg.openshift.redhat.com/broker/rest/user
> * Adding handle: conn: 0x178dae0
> * Adding handle: send: 0
> * Adding handle: recv: 0
> * Curl_addHandleToPipeline: length: 1
> * - Conn 0 (0x178dae0) send_pipe: 1, recv_pipe: 0
> * About to connect() to proxy file.rdu.redhat.com port 3128 (#0)
> * Trying 10.11.5.7...
> * Connected to file.rdu.redhat.com (10.11.5.7) port 3128 (#0)
> * Establish HTTP proxy tunnel to stg.openshift.redhat.com:443
> * Server auth using Basic with user 'adietish(a)redhat.com'
> > CONNECT stg.openshift.redhat.com:443 HTTP/1.1
> > Host: stg.openshift.redhat.com:443
> > User-Agent: curl/7.32.0
> > Proxy-Connection: Keep-Alive
> >
> < HTTP/1.0 200 Connection established
> <
> * Proxy replied OK to CONNECT request
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> * CAfile: /etc/pki/tls/certs/ca-bundle.crt
> CApath: none
> * SSL connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA
> * Server certificate:
> * subject: CN=stg.openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US
> * start date: Apr 30 00:00:00 2014 GMT
> * expire date: May 04 12:00:00 2016 GMT
> * common name: stg.openshift.redhat.com
> * issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
> * Server auth using Basic with user 'adietish(a)redhat.com'
> > GET /broker/rest/user HTTP/1.1
> > Authorization: Basic YWRpZXRpc2hAcmVkaGF0LmNvbTpib2d1cw==
> > User-Agent: curl/7.32.0
> > Host: stg.openshift.redhat.com
> > Accept: */*
> >
> < HTTP/1.1 401
> < Date: Wed, 24 Sep 2014 10:19:22 GMT
> * Server Apache/2.2.15 (Red Hat) is not blacklisted
> < Server: Apache/2.2.15 (Red Hat)
> < X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21
> * Authentication problem. Ignoring this.
> < WWW-Authenticate: Basic realm="Application"
> < X-UA-Compatible: IE=Edge,chrome=1
> < Cache-Control: no-cache, private
> < X-Request-Id: 5217138e18f0e036b1880d006e4c3cb6
> < X-Runtime: 0.569233
> < X-Rack-Cache: miss
> < Status: 401
> < Content-Length: 27
> < Content-Type: text/html; charset=utf-8
> < Vary: Accept-Encoding,User-Agent
> < Strict-Transport-Security: max-age=15768000, includeSubDomains
> < ProxyTime: D=574882
> <
> HTTP Basic: Access denied.
> * Connection #0 to host file.rdu.redhat.com left intact
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months