date:20170608

[jira] [Resolved] (KNOX-932) Option to remove the server-name from HTTP-header response

2017-06-08 Thread Larry McCay (JIRA)


 [ 
https://issues.apache.org/jira/browse/KNOX-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay resolved KNOX-932.
--
Resolution: Fixed

[~ljmiv] - I've just committed this to master and it will be in the 0.13.0 
release.
Thank you for the contribution!

> Option to remove the server-name from HTTP-header response 
> ---
>
> Key: KNOX-932
> URL: https://issues.apache.org/jira/browse/KNOX-932
> Project: Apache Knox
>  Issue Type: Improvement
>Reporter: Kunal Rajguru
>Assignee: Lawrence McCay IV
>  Labels: http-headers
> Fix For: 0.13.0
>
> Attachments: KNOX-932-001.patch
>
>
> Option to remove the server name which is sent as HTTP-Header in the response 
> For example :
> curl -i -k -u : -X GET 
> 'https://localhost:8443/gateway/default/webhdfs/v1/?op=LISTSTATUS'
> HTTP/1.1 200 OK 
> Set-Cookie: 
> JSESSIONID=fs2lu9w7jcgt1tshnfs1cqf8v;Path=/gateway/default;Secure;HttpOnly 
> Expires: Thu, 01 Jan 1970 00:00:00 GMT 
> Cache-Control: no-cache 
> Expires: Wed, 15 Mar 2017 12:49:24 GMT 
> Date: Wed, 15 Mar 2017 12:49:24 GMT 
> Pragma: no-cache 
> Expires: Wed, 15 Mar 2017 12:49:24 GMT 
> Date: Wed, 15 Mar 2017 12:49:24 GMT 
> Pragma: no-cache 
> Server: Jetty(6.1.26.hwx) 
> Content-Type: application/json 
> Content-Length: 2593



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (KNOX-932) Option to remove the server-name from HTTP-header response

2017-06-08 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/KNOX-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043868#comment-16043868
 ] 

ASF subversion and git services commented on KNOX-932:
--

Commit f4ccdfd696bca10c73e7a7e336d9e72d4db423b5 in knox's branch 
refs/heads/master from [~lmccay]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=f4ccdfd ]

KNOX-932 - Option to remove the server-name from HTTP-header response (Lawrence 
McCay IV via lmccay)

> Option to remove the server-name from HTTP-header response 
> ---
>
> Key: KNOX-932
> URL: https://issues.apache.org/jira/browse/KNOX-932
> Project: Apache Knox
>  Issue Type: Improvement
>Reporter: Kunal Rajguru
>Assignee: Lawrence McCay IV
>  Labels: http-headers
> Fix For: 0.13.0
>
> Attachments: KNOX-932-001.patch
>
>
> Option to remove the server name which is sent as HTTP-Header in the response 
> For example :
> curl -i -k -u : -X GET 
> 'https://localhost:8443/gateway/default/webhdfs/v1/?op=LISTSTATUS'
> HTTP/1.1 200 OK 
> Set-Cookie: 
> JSESSIONID=fs2lu9w7jcgt1tshnfs1cqf8v;Path=/gateway/default;Secure;HttpOnly 
> Expires: Thu, 01 Jan 1970 00:00:00 GMT 
> Cache-Control: no-cache 
> Expires: Wed, 15 Mar 2017 12:49:24 GMT 
> Date: Wed, 15 Mar 2017 12:49:24 GMT 
> Pragma: no-cache 
> Expires: Wed, 15 Mar 2017 12:49:24 GMT 
> Date: Wed, 15 Mar 2017 12:49:24 GMT 
> Pragma: no-cache 
> Server: Jetty(6.1.26.hwx) 
> Content-Type: application/json 
> Content-Length: 2593



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (KNOX-932) Option to remove the server-name from HTTP-header response

2017-06-08 Thread Larry McCay (JIRA)


[ 
https://issues.apache.org/jira/browse/KNOX-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043853#comment-16043853
 ] 

Larry McCay commented on KNOX-932:
--

[~ljmiv] - Thank you for your contribution!
I will review your patch shortly and will hopefully get it into 0.13.0 release.

> Option to remove the server-name from HTTP-header response 
> ---
>
> Key: KNOX-932
> URL: https://issues.apache.org/jira/browse/KNOX-932
> Project: Apache Knox
>  Issue Type: Improvement
>Reporter: Kunal Rajguru
>Assignee: Lawrence McCay IV
>  Labels: http-headers
> Fix For: 0.13.0
>
> Attachments: KNOX-932-001.patch
>
>
> Option to remove the server name which is sent as HTTP-Header in the response 
> For example :
> curl -i -k -u : -X GET 
> 'https://localhost:8443/gateway/default/webhdfs/v1/?op=LISTSTATUS'
> HTTP/1.1 200 OK 
> Set-Cookie: 
> JSESSIONID=fs2lu9w7jcgt1tshnfs1cqf8v;Path=/gateway/default;Secure;HttpOnly 
> Expires: Thu, 01 Jan 1970 00:00:00 GMT 
> Cache-Control: no-cache 
> Expires: Wed, 15 Mar 2017 12:49:24 GMT 
> Date: Wed, 15 Mar 2017 12:49:24 GMT 
> Pragma: no-cache 
> Expires: Wed, 15 Mar 2017 12:49:24 GMT 
> Date: Wed, 15 Mar 2017 12:49:24 GMT 
> Pragma: no-cache 
> Server: Jetty(6.1.26.hwx) 
> Content-Type: application/json 
> Content-Length: 2593



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (KNOX-932) Option to remove the server-name from HTTP-header response

2017-06-08 Thread Larry McCay (JIRA)


 [ 
https://issues.apache.org/jira/browse/KNOX-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay reassigned KNOX-932:


Assignee: Lawrence McCay IV  (was: Krishna Pandey)

> Option to remove the server-name from HTTP-header response 
> ---
>
> Key: KNOX-932
> URL: https://issues.apache.org/jira/browse/KNOX-932
> Project: Apache Knox
>  Issue Type: Improvement
>Reporter: Kunal Rajguru
>Assignee: Lawrence McCay IV
>  Labels: http-headers
> Fix For: 0.13.0
>
> Attachments: KNOX-932-001.patch
>
>
> Option to remove the server name which is sent as HTTP-Header in the response 
> For example :
> curl -i -k -u : -X GET 
> 'https://localhost:8443/gateway/default/webhdfs/v1/?op=LISTSTATUS'
> HTTP/1.1 200 OK 
> Set-Cookie: 
> JSESSIONID=fs2lu9w7jcgt1tshnfs1cqf8v;Path=/gateway/default;Secure;HttpOnly 
> Expires: Thu, 01 Jan 1970 00:00:00 GMT 
> Cache-Control: no-cache 
> Expires: Wed, 15 Mar 2017 12:49:24 GMT 
> Date: Wed, 15 Mar 2017 12:49:24 GMT 
> Pragma: no-cache 
> Expires: Wed, 15 Mar 2017 12:49:24 GMT 
> Date: Wed, 15 Mar 2017 12:49:24 GMT 
> Pragma: no-cache 
> Server: Jetty(6.1.26.hwx) 
> Content-Type: application/json 
> Content-Length: 2593



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (KNOX-932) Option to remove the server-name from HTTP-header response

2017-06-08 Thread Lawrence McCay IV (JIRA)


 [ 
https://issues.apache.org/jira/browse/KNOX-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lawrence McCay IV updated KNOX-932:
---
Attachment: KNOX-932-001.patch

> Option to remove the server-name from HTTP-header response 
> ---
>
> Key: KNOX-932
> URL: https://issues.apache.org/jira/browse/KNOX-932
> Project: Apache Knox
>  Issue Type: Improvement
>Reporter: Kunal Rajguru
>Assignee: Krishna Pandey
>  Labels: http-headers
> Fix For: 0.13.0
>
> Attachments: KNOX-932-001.patch
>
>
> Option to remove the server name which is sent as HTTP-Header in the response 
> For example :
> curl -i -k -u : -X GET 
> 'https://localhost:8443/gateway/default/webhdfs/v1/?op=LISTSTATUS'
> HTTP/1.1 200 OK 
> Set-Cookie: 
> JSESSIONID=fs2lu9w7jcgt1tshnfs1cqf8v;Path=/gateway/default;Secure;HttpOnly 
> Expires: Thu, 01 Jan 1970 00:00:00 GMT 
> Cache-Control: no-cache 
> Expires: Wed, 15 Mar 2017 12:49:24 GMT 
> Date: Wed, 15 Mar 2017 12:49:24 GMT 
> Pragma: no-cache 
> Expires: Wed, 15 Mar 2017 12:49:24 GMT 
> Date: Wed, 15 Mar 2017 12:49:24 GMT 
> Pragma: no-cache 
> Server: Jetty(6.1.26.hwx) 
> Content-Type: application/json 
> Content-Length: 2593



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (KNOX-965) SecureQueryDecryptProcessor decode call could return null thus it would get a NPE

2017-06-08 Thread Jeffrey E Rodriguez (JIRA)

Jeffrey E  Rodriguez created KNOX-965:
-

 Summary: SecureQueryDecryptProcessor decode call could return null 
thus it  would get a NPE
 Key: KNOX-965
 URL: https://issues.apache.org/jira/browse/KNOX-965
 Project: Apache Knox
  Issue Type: Bug
  Components: Server
Affects Versions: 0.11.0, 0.12.0, 0.13.0
 Environment: All
Reporter: Jeffrey E  Rodriguez
Assignee: Jeffrey E  Rodriguez
 Fix For: 0.13.0


SecureQueryDecryptProcessor decode call could return null thus it  would get a 
NPE

We should look for decode return value and it is null should return :
UrlRewriteStepStatus.FAILURE instead of try to process return null value.

For example if encode fail you may get:

Failed to rewrite URL: 
https://edl-test-primary.bde-np.info53.com:8443/gateway/default/webhdfs/data/v1/webhdfs/v1/landing/incoming/bcaps/TEMPG_TBA_OAFAPV10_MSTR_APP_VER_PAYMENT_SCHEDULE/TEMPG_TBA_OAFAPV10_MSTR_APP_VER_PAYMENT_SCHEDULE.del?_=CBCQPRSZG4oUO6HBLU0Jhgy7Uzxx1SqYAyMtiwpBg2BYbeQwuoeCCaT7ZuP98H1XYHAvnDtPEiWPSZ5E9L_wfgk8feUD1KRMNPtV4JcYs5HZQxV7DLNHJ2U4TS_3ozHHQIr92g0gUNH1wcLWVYwlEy5YKUC-tGKlMBBaJdlbvJ426hoLVfh4g3RuEG_-m3-DRu8nnoccpjeh3DsO1Z9S7zPfzXIl5lkLznfd,
 direction: IN, rule: WEBHDFS/webhdfs/inbound/datanode
java.lang.NullPointerException
at java.util.StringTokenizer.(StringTokenizer.java:199)
at java.util.StringTokenizer.(StringTokenizer.java:221)
at 
org.apache.hadoop.gateway.securequery.SecureQueryDecryptProcessor.process(SecureQueryDecryptProcessor.java:66)
at 
org.apache.hadoop.gateway.filter.rewrite.impl.UrlRewriteStepProcessorHolder.process(UrlRewriteStepProcessorHolder.java:101)
at 
org.apache.hadoop.gateway.filter.rewrite.impl.UrlRewriteStepProcessorHolder.processActions(UrlRewriteStepProcessorHolder.java:199)
at 
org.apache.hadoop.gateway.filter.rewrite.impl.UrlRewriteStepProcessorHolder.processAndFlow(UrlRewriteStepProcessorHolder.java:156)
at 
org.apache.hadoop.gateway.filter.rewrite.impl.UrlRewriteStepProcessorHolder.process(UrlRewriteStepProcessorHolder.java:114)
at 
org.apache.hadoop.gateway.filter.rewrite.api.UrlRewriteProcessor.rewrite(UrlRewriteProcessor.java:151)
at 
org.apache.hadoop.gateway.filter.rewrite.impl.UrlRewriteRequest.getTargetUrl(UrlRewriteRequest.java:114)
at 
org.apache.hadoop.gateway.filter.rewrite.impl.UrlRewriteRequest.getRequestURI(UrlRewriteRequest.java:141)
at 
org.apache.hadoop.gateway.filter.rewrite.impl.UrlRewriteRequest.getRequestURL(UrlRewriteRequest.java:134)
at 
javax.servlet.http.HttpServletRequestWrapper.getRequestURL(HttpServletRequestWrapper.java:241)
at 
org.apache.hadoop.gateway.dispatch.GatewayDispatchFilter.getDispatchUrl(GatewayDispatchFilter.java:116)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (KNOX-949) WeBHDFS proxy replaces %20 encoded spaces in URL with + encoding

2017-06-08 Thread Larry McCay (JIRA)


 [ 
https://issues.apache.org/jira/browse/KNOX-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay updated KNOX-949:
-
Status: Patch Available  (was: Open)

> WeBHDFS proxy replaces %20 encoded spaces in URL with + encoding
> 
>
> Key: KNOX-949
> URL: https://issues.apache.org/jira/browse/KNOX-949
> Project: Apache Knox
>  Issue Type: Bug
>Affects Versions: 0.11.0
>Reporter: Alex Willmer
>Assignee: Larry McCay
>Priority: Blocker
> Fix For: 0.13.0
>
> Attachments: KNOX-949-001.patch
>
>
> If a file with spaces in the name (e.g. {{foo bar.txt}}) is requested from 
> HDFS, through WebHDFS and Knox - then Knox rewrites the {{%20}} encoding in 
> the URL sent by the client, with {{+}} encoding (e.g. {{foo%20bar.txt}} -> 
> {{foo+bar.txt}}). This results in an HTTP 404 being returned by WebHDFS, and 
> hence by Knox. Requesting the same file directly from WebHDFS works. Example
> Client request
> {noformat}
> curl 
> "https://:18443/gateway//webhdfs/v1/docs/filename%20with%20spaces.pdf?op=OPEN"
>  \
>  -: -k -s
> {noformat}
> Knox response body
> {noformat}
> {"exception":"FileNotFoundException",
>  "javaClassName":"java.io.FileNotFoundException",
>  "message":"File /docs/filename+with+spaces.pdf not found."}
> {noformat}
> Knox logs
> {noformat}
> ==> /var/log/hadoop/knox/gateway-audit.log <==
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSaccess|uri|/gateway//webhdfs/v1/docs/filename
> with spaces.pdf?op=OPEN|unavailable|Request method: GET
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSauthentication|uri|/gateway//webhdfs/v1/docs/filename
> with spaces.pdf?op=OPEN|success|
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSauthentication|uri|/gateway//webhdfs/v1/docs/filename
> with spaces.pdf?op=OPEN|success|Groups: []
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSauthorization|uri|/gateway//webhdfs/v1/docs/filename
> with spaces.pdf?op=OPEN|success|
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSdispatch|uri|http://.:50070/webhdfs/v1/docs/filename+with+spaces.pdf?op=OPEN=|unavailable|Request
> method: GET
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSdispatch|uri|http://.:50070/webhdfs/v1/docs/filename+with+spaces.pdf?op=OPEN=|success|Response
> status: 404
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSaccess|uri|/gateway//webhdfs/v1/docs/filename
> with spaces.pdf?op=OPEN|success|Response status: 404
> ==> /var/log/hadoop/knox/gateway.log <==
> 2017-05-24 15:51:05,254 INFO  hadoop.gateway 
> (KnoxLdapRealm.java:getUserDn(691)) - Computed
> userDn: uid=,cn=users,cn=accounts,dc= using dnTemplate for
> principal: 
> 2017-05-24 15:51:05,259 INFO  hadoop.gateway 
> (AclsAuthorizationFilter.java:doFilter(85)) -
> Access Granted: true
> {noformat}
> Direct WebHDFS request for the same file
> {noformat}
> # curl -si -u: 
> "http://:50070/webhdfs/v1/docs/filename%20with%20spaces.pdf?op=OPEN"
> --negotiate -L | head -n40
> HTTP/1.1 401 Authentication required
> Cache-Control: must-revalidate,no-cache,no-store
> Date: Wed, 24 May 2017 19:01:41 GMT
> Pragma: no-cache
> Date: Wed, 24 May 2017 19:01:41 GMT
> Pragma: no-cache
> X-FRAME-OPTIONS: SAMEORIGIN
> WWW-Authenticate: Negotiate
> Set-Cookie: hadoop.auth=; Path=/; HttpOnly
> Content-Type: text/html; charset=iso-8859-1
> Content-Length: 1533
> Server: Jetty(6.1.26.hwx)
> HTTP/1.1 307 TEMPORARY_REDIRECT
> Cache-Control: no-cache
> Expires: Wed, 24 May 2017 19:01:42 GMT
> Date: Wed, 24 May 2017 19:01:42 GMT
> Pragma: no-cache
> Expires: Wed, 24 May 2017 19:01:42 GMT
> Date: Wed, 24 May 2017 19:01:42 GMT
> Pragma: no-cache
> X-FRAME-OPTIONS: SAMEORIGIN
> WWW-Authenticate: Negotiate 
> YGkGCSqGSIb3EgECAgIAb1owWKADAgEFoQMCAQ+iTDBKoAMCARKiQwRBQM/auuLcl2xey6wMp6EjCPJFSqK3snscxMzW7RvfgxOo7182GzD5N9jf+OWGr+tjpvlRX0c/7iTBfYKSetf4ekU=
> Set-Cookie: 
> hadoop.auth="u=admin=admin@CYSAFA=kerberos=1495688502002=b7p35TgaxItAUTkKJuSXuynoq9E=";
> Path=/; HttpOnly
> Content-Type: application/octet-stream
> Location: 
> http://:1022/webhdfs/v1/docs/filename%20with%20spaces.pdf?op=OPEN=HgAFYWRtaW4FYWRtaW4AigFcO9YJ8ooBXF_ijfJFAxSBYFUnsXY3up11ZNIi4hIi__5RvRJXRUJIREZTIGRlbGVnYXRpb24PMTcyLjE4LjAuOTo4MDIw=:8020=0
> Content-Length: 0
> Server: Jetty(6.1.26.hwx)
> HTTP/1.1 200 OK
> Access-Control-Allow-Methods: GET
> Access-Control-Allow-Origin: *
> Content-Type: application/octet-stream
> Connection: close
> Content-Length: 13365618
> %1.6
> <>stream
> ...
> {noformat}
> See also
>  - 
> http://mail-archives.apache.org/mod_mbox/knox-user/201705.mbox/%3C335C4DD06CF6C24EAA7A73F44D43D7CB4E6EB300%40SE-EX021.groupinfra.com%3E

[jira] [Assigned] (KNOX-949) WeBHDFS proxy replaces %20 encoded spaces in URL with + encoding

2017-06-08 Thread Larry McCay (JIRA)


 [ 
https://issues.apache.org/jira/browse/KNOX-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay reassigned KNOX-949:


Assignee: Larry McCay

> WeBHDFS proxy replaces %20 encoded spaces in URL with + encoding
> 
>
> Key: KNOX-949
> URL: https://issues.apache.org/jira/browse/KNOX-949
> Project: Apache Knox
>  Issue Type: Bug
>Affects Versions: 0.11.0
>Reporter: Alex Willmer
>Assignee: Larry McCay
>Priority: Blocker
> Fix For: 0.13.0
>
>
> If a file with spaces in the name (e.g. {{foo bar.txt}}) is requested from 
> HDFS, through WebHDFS and Knox - then Knox rewrites the {{%20}} encoding in 
> the URL sent by the client, with {{+}} encoding (e.g. {{foo%20bar.txt}} -> 
> {{foo+bar.txt}}). This results in an HTTP 404 being returned by WebHDFS, and 
> hence by Knox. Requesting the same file directly from WebHDFS works. Example
> Client request
> {noformat}
> curl 
> "https://:18443/gateway//webhdfs/v1/docs/filename%20with%20spaces.pdf?op=OPEN"
>  \
>  -: -k -s
> {noformat}
> Knox response body
> {noformat}
> {"exception":"FileNotFoundException",
>  "javaClassName":"java.io.FileNotFoundException",
>  "message":"File /docs/filename+with+spaces.pdf not found."}
> {noformat}
> Knox logs
> {noformat}
> ==> /var/log/hadoop/knox/gateway-audit.log <==
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSaccess|uri|/gateway//webhdfs/v1/docs/filename
> with spaces.pdf?op=OPEN|unavailable|Request method: GET
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSauthentication|uri|/gateway//webhdfs/v1/docs/filename
> with spaces.pdf?op=OPEN|success|
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSauthentication|uri|/gateway//webhdfs/v1/docs/filename
> with spaces.pdf?op=OPEN|success|Groups: []
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSauthorization|uri|/gateway//webhdfs/v1/docs/filename
> with spaces.pdf?op=OPEN|success|
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSdispatch|uri|http://.:50070/webhdfs/v1/docs/filename+with+spaces.pdf?op=OPEN=|unavailable|Request
> method: GET
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSdispatch|uri|http://.:50070/webhdfs/v1/docs/filename+with+spaces.pdf?op=OPEN=|success|Response
> status: 404
> 17/05/24 15:51:05 
> ||88ce58ea-d7c5-46cd-a87a-c2f96b38130e|audit|WEBHDFSaccess|uri|/gateway//webhdfs/v1/docs/filename
> with spaces.pdf?op=OPEN|success|Response status: 404
> ==> /var/log/hadoop/knox/gateway.log <==
> 2017-05-24 15:51:05,254 INFO  hadoop.gateway 
> (KnoxLdapRealm.java:getUserDn(691)) - Computed
> userDn: uid=,cn=users,cn=accounts,dc= using dnTemplate for
> principal: 
> 2017-05-24 15:51:05,259 INFO  hadoop.gateway 
> (AclsAuthorizationFilter.java:doFilter(85)) -
> Access Granted: true
> {noformat}
> Direct WebHDFS request for the same file
> {noformat}
> # curl -si -u: 
> "http://:50070/webhdfs/v1/docs/filename%20with%20spaces.pdf?op=OPEN"
> --negotiate -L | head -n40
> HTTP/1.1 401 Authentication required
> Cache-Control: must-revalidate,no-cache,no-store
> Date: Wed, 24 May 2017 19:01:41 GMT
> Pragma: no-cache
> Date: Wed, 24 May 2017 19:01:41 GMT
> Pragma: no-cache
> X-FRAME-OPTIONS: SAMEORIGIN
> WWW-Authenticate: Negotiate
> Set-Cookie: hadoop.auth=; Path=/; HttpOnly
> Content-Type: text/html; charset=iso-8859-1
> Content-Length: 1533
> Server: Jetty(6.1.26.hwx)
> HTTP/1.1 307 TEMPORARY_REDIRECT
> Cache-Control: no-cache
> Expires: Wed, 24 May 2017 19:01:42 GMT
> Date: Wed, 24 May 2017 19:01:42 GMT
> Pragma: no-cache
> Expires: Wed, 24 May 2017 19:01:42 GMT
> Date: Wed, 24 May 2017 19:01:42 GMT
> Pragma: no-cache
> X-FRAME-OPTIONS: SAMEORIGIN
> WWW-Authenticate: Negotiate 
> YGkGCSqGSIb3EgECAgIAb1owWKADAgEFoQMCAQ+iTDBKoAMCARKiQwRBQM/auuLcl2xey6wMp6EjCPJFSqK3snscxMzW7RvfgxOo7182GzD5N9jf+OWGr+tjpvlRX0c/7iTBfYKSetf4ekU=
> Set-Cookie: 
> hadoop.auth="u=admin=admin@CYSAFA=kerberos=1495688502002=b7p35TgaxItAUTkKJuSXuynoq9E=";
> Path=/; HttpOnly
> Content-Type: application/octet-stream
> Location: 
> http://:1022/webhdfs/v1/docs/filename%20with%20spaces.pdf?op=OPEN=HgAFYWRtaW4FYWRtaW4AigFcO9YJ8ooBXF_ijfJFAxSBYFUnsXY3up11ZNIi4hIi__5RvRJXRUJIREZTIGRlbGVnYXRpb24PMTcyLjE4LjAuOTo4MDIw=:8020=0
> Content-Length: 0
> Server: Jetty(6.1.26.hwx)
> HTTP/1.1 200 OK
> Access-Control-Allow-Methods: GET
> Access-Control-Allow-Origin: *
> Content-Type: application/octet-stream
> Connection: close
> Content-Length: 13365618
> %1.6
> <>stream
> ...
> {noformat}
> See also
>  - 
> http://mail-archives.apache.org/mod_mbox/knox-user/201705.mbox/%3C335C4DD06CF6C24EAA7A73F44D43D7CB4E6EB300%40SE-EX021.groupinfra.com%3E



--
This message was sent by Atlassian JIRA

[jira] [Updated] (KNOX-759) jansi dependency causes issues starting knox shell

2017-06-08 Thread Colm O hEigeartaigh (JIRA)


 [ 
https://issues.apache.org/jira/browse/KNOX-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colm O hEigeartaigh updated KNOX-759:
-
Attachment: 0001-KNOX-759-jansi-dependency-causes-issues-starting-kno.patch


See attached a patch to update jansi to the latest version (1.16). Confirmed 
that the problem reported on windows goes away, and that the shell works fine 
on linux after the upgrade.

Feel free to bump this to 0.14.0

> jansi dependency causes issues starting knox shell
> --
>
> Key: KNOX-759
> URL: https://issues.apache.org/jira/browse/KNOX-759
> Project: Apache Knox
>  Issue Type: Bug
>  Components: ClientDSL
>Affects Versions: 0.9.1
> Environment: windows 7
>Reporter: Cole Ferrier
>Assignee: Colm O hEigeartaigh
> Fix For: 0.13.0
>
> Attachments: 
> 0001-KNOX-759-jansi-dependency-causes-issues-starting-kno.patch
>
>
> Using knox .9.1 downloaded today. i unzipped it in windows and attemped to 
> run java -jar bin\shell.jar from the extracted directory. it errored with:
> FATAL: java.lang.NoSuchMethodError: 
> org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> java.lang.NoSuchMethodError: 
> org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> at 
> jline.WindowsTerminal.getConsoleOutputCodepage(WindowsTerminal.java:295)
> at jline.WindowsTerminal.getOutputEncoding(WindowsTerminal.java:185)
> at jline.console.ConsoleReader.(ConsoleReader.java:242)
> at jline.console.ConsoleReader.(ConsoleReader.java:232)
> at jline.console.ConsoleReader.(ConsoleReader.java:224)
> at 
> org.codehaus.groovy.tools.shell.PatchedConsoleReader.(PatchedConsoleReader.groovy:32)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown 
> Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown 
> Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at 
> org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
> at 
> org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105)
> at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:60)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:235)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:255)
> at 
> org.codehaus.groovy.tools.shell.InteractiveShellRunner.(InteractiveShellRunner.groovy:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown 
> Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown 
> Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at 
> org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
> at 
> org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
> at 
> org.codehaus.groovy.runtime.callsite.ConstructorSite.callConstructor(ConstructorSite.java:45)
> at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:60)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:235)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:255)
> at org.codehaus.groovy.tools.shell.Groovysh.run(Groovysh.groovy:574)
> at org.apache.hadoop.gateway.shell.Shell.main(Shell.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> if you replace the jansi-1.6.jar file that is in the dep folder with the 1.12 
> version from:
> http://fusesource.github.io/jansi/download.html
> the shell starts as expected.
> I didn't test any of the intermediate jar levels.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (KNOX-759) jansi dependency causes issues starting knox shell

2017-06-08 Thread Colm O hEigeartaigh (JIRA)


 [ 
https://issues.apache.org/jira/browse/KNOX-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colm O hEigeartaigh updated KNOX-759:
-
Fix Version/s: 0.13.0

> jansi dependency causes issues starting knox shell
> --
>
> Key: KNOX-759
> URL: https://issues.apache.org/jira/browse/KNOX-759
> Project: Apache Knox
>  Issue Type: Bug
>  Components: ClientDSL
>Affects Versions: 0.9.1
> Environment: windows 7
>Reporter: Cole Ferrier
>Assignee: Colm O hEigeartaigh
> Fix For: 0.13.0
>
>
> Using knox .9.1 downloaded today. i unzipped it in windows and attemped to 
> run java -jar bin\shell.jar from the extracted directory. it errored with:
> FATAL: java.lang.NoSuchMethodError: 
> org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> java.lang.NoSuchMethodError: 
> org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> at 
> jline.WindowsTerminal.getConsoleOutputCodepage(WindowsTerminal.java:295)
> at jline.WindowsTerminal.getOutputEncoding(WindowsTerminal.java:185)
> at jline.console.ConsoleReader.(ConsoleReader.java:242)
> at jline.console.ConsoleReader.(ConsoleReader.java:232)
> at jline.console.ConsoleReader.(ConsoleReader.java:224)
> at 
> org.codehaus.groovy.tools.shell.PatchedConsoleReader.(PatchedConsoleReader.groovy:32)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown 
> Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown 
> Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at 
> org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
> at 
> org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105)
> at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:60)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:235)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:255)
> at 
> org.codehaus.groovy.tools.shell.InteractiveShellRunner.(InteractiveShellRunner.groovy:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown 
> Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown 
> Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at 
> org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
> at 
> org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
> at 
> org.codehaus.groovy.runtime.callsite.ConstructorSite.callConstructor(ConstructorSite.java:45)
> at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:60)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:235)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:255)
> at org.codehaus.groovy.tools.shell.Groovysh.run(Groovysh.groovy:574)
> at org.apache.hadoop.gateway.shell.Shell.main(Shell.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> if you replace the jansi-1.6.jar file that is in the dep folder with the 1.12 
> version from:
> http://fusesource.github.io/jansi/download.html
> the shell starts as expected.
> I didn't test any of the intermediate jar levels.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Groovy SSL configuration

2017-06-08 Thread larry mccay

+1!!!

On Thu, Jun 8, 2017 at 9:44 AM, Colm O hEigeartaigh 
wrote:

> Thanks Larry, it's working now.
>
> Colm.
>
> On Thu, Jun 8, 2017 at 12:37 PM, larry mccay 
> wrote:
>
> > Hi Colm -
> >
> > See the Client Shell Quick Start section in the Users Guide:
> > http://knox.apache.org/books/knox-0-12-0/user-guide.html#
> Client+Quickstart
> >
> > Steps #3 and #4 should be all you need to do.
> >
> > HTH,
> >
> > --larry
> >
> > On Thu, Jun 8, 2017 at 6:40 AM, Colm O hEigeartaigh  >
> > wrote:
> >
> >> How do I specify the SSL truststore when using the 'bin/shell.jar'? All
> of
> >> the examples I can find don't seem to configure the truststore, yet I
> get
> >> the following error:
> >>
> >> javax.net.ssl.SSLHandshakeException:
> >> sun.security.validator.ValidatorException: PKIX path building failed:
> >> sun.security.provider.certpath.SunCertPathBuilderException: unable to
> >> find
> >> valid certification path to requested target
> >>
> >> Colm.
> >>
> >>
> >> --
> >> Colm O hEigeartaigh
> >>
> >> Talend Community Coder
> >> http://coders.talend.com
> >>
> >
> >
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>

Re: Groovy SSL configuration

2017-06-08 Thread Colm O hEigeartaigh

Thanks Larry, it's working now.

Colm.

On Thu, Jun 8, 2017 at 12:37 PM, larry mccay  wrote:

> Hi Colm -
>
> See the Client Shell Quick Start section in the Users Guide:
> http://knox.apache.org/books/knox-0-12-0/user-guide.html#Client+Quickstart
>
> Steps #3 and #4 should be all you need to do.
>
> HTH,
>
> --larry
>
> On Thu, Jun 8, 2017 at 6:40 AM, Colm O hEigeartaigh 
> wrote:
>
>> How do I specify the SSL truststore when using the 'bin/shell.jar'? All of
>> the examples I can find don't seem to configure the truststore, yet I get
>> the following error:
>>
>> javax.net.ssl.SSLHandshakeException:
>> sun.security.validator.ValidatorException: PKIX path building failed:
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to
>> find
>> valid certification path to requested target
>>
>> Colm.
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: [DISCUSS] Planning for Apache Knox 0.13.0 (1.0.0) Release

2017-06-08 Thread larry mccay

All -

Just an FYI - I am currently trying to resolve a number of url encoding
related issues that were introduced by a change to get proxying of Ambari
UI working properly.

Personally, I feel this is a blocker and would like to get a fix in for
0.13.0.
At the same time, we may determine that most of the issues are edge cases
or at least not very common.
I am aware of WebHDFS issues with spaces in the filename or path and HBase
related issues where reserved characters such as '/' are being used.

It appears that this has been introduced by trying to accommodate Ambari's
use of an unwise character '|' in its URLs.
A general approach of encoding and decoding the URL has led to a number of
inconsistencies with what the backend services expect.

I will attempt to find the most surgical and least invasive fix for this
issue as to reduce risk for 0.13.0 closedown.

thanks,

--larry

On Wed, May 24, 2017 at 9:49 AM, Sandeep More  wrote:

> Ah ! got it.
>
>
> On Wed, May 24, 2017 at 9:46 AM, larry mccay  wrote:
>
>> Actually, what I am proposing is that we *branch* on Monday and double
>> commit as necessary in order to close down before the rc and through the
>> release process. I'd like to get to a rc by the end of next week - 6/2 - if
>> not sooner.
>>
>> We will also likely need to double commit bug fixes to master and 0.13.0
>> branch for some time in case we need a new 0.13.x release to avoid the
>> 1.0.0 refactoring for existing deployments.
>>
>> On Wed, May 24, 2017 at 9:29 AM, Sandeep More 
>> wrote:
>>
>>> Hello Larry,
>>>
>>> Thanks for starting the discussion, given that we are away from the
>>> target date just by a week I too think that releasing 0.13.0 on Monday and
>>> then working towards 1.0.0 (package refactoring) would be a good idea. One
>>> upshot of this is that we don't have to double commit as we had initially
>>> thought :)
>>>
>>> Best,
>>> Sandeep
>>>
>>> On Tue, May 23, 2017 at 4:44 PM, larry mccay  wrote:
>>>
 All -

 As we targeted a 5/31 date for the release of 0.13.0, I think we need
 to look at managing the current scope for 0.13.0 as well as the plan for a
 1.0.0 again.
 Since we are just a week away from the target date, I think that
 refactoring the package names for the 1.0.0 release at the same time is a
 stretch.

 We currently have 22 or so JIRAs and will not be able to get them all
 into 0.13.0.
 What do you think about the following:

 * We manage the existing scope over the rest of this week.
 * I will post comments on some JIRAs about potentially moving them out
 and without any movement will move them out by Friday 26th.
 * JIRAs that I think are outside the KIPs that are driving the release
 or that may destabilize the release I will just move.

 If I move something that is something wanted by you, please feel free
 to add it back, comment or raise discussion on this thread.

 I also propose that we branch for 0.13.0 on Monday 5/29th and work
 toward getting the rest of the required issues in and an RC by the 31st or
 by end of the week. Once we release 0.13.0, we should refactor master for
 the 1.0.0 release - concentrate on closing down any fallout from package
 name changes and do an immediate 1.0.0 release.

 Thoughts?

 thanks,

 --larry

 On Thu, Apr 27, 2017 at 1:32 PM, Sandeep More 
 wrote:

> Sounds great !
>
> On Thu, Apr 27, 2017 at 12:32 PM, larry mccay 
> wrote:
>
> > That sounds reasonable to me.
> > I was hoping to get as many of the patches available and important
> bugs
> > fixed before the split as well.
> > Minimizing the double commits/patches is definitely in our interest.
> >
> > At the same time, we need to have enough time to spend on
> refactoring as
> > well.
> > I'm thinking that May 15th may be a good branch point - giving us 2
> weeks
> > to concentrate on repackaging and adapter classes.
> >
> >
> > On Thu, Apr 27, 2017 at 12:16 PM, Sandeep More <
> moresand...@gmail.com>
> > wrote:
> >
> > > Oh, I guess it depends on when we split, I was planning on taking
> up the
> > > new feature (mentioned in earlier email).
> > > If we decide to go for the feature I was hoping to get it in sooner
> > (before
> > > the split) if possible.
> > >
> > >
> > > On Thu, Apr 27, 2017 at 11:53 AM, larry mccay 
> wrote:
> > >
> > > > Actually, I meant 5/31 for a release date.
> > > > You think that is too early for a repackaged and narrowly scoped
> 1.0.0?
> > > >
> > > > On Thu, Apr 27, 2017 at 11:46 AM, Sandeep More <
> moresand...@gmail.com>
> > > > wrote:
> > > >
> > > > > Great, thanks

[jira] [Assigned] (KNOX-738) Remove references to deprecated httpclient class DefaultHttpClient

2017-06-08 Thread Colm O hEigeartaigh (JIRA)


 [ 
https://issues.apache.org/jira/browse/KNOX-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colm O hEigeartaigh reassigned KNOX-738:


Assignee: Colm O hEigeartaigh  (was: Sumit Gupta)

> Remove references to deprecated httpclient class DefaultHttpClient
> --
>
> Key: KNOX-738
> URL: https://issues.apache.org/jira/browse/KNOX-738
> Project: Apache Knox
>  Issue Type: Bug
>Reporter: Sumit Gupta
>Assignee: Colm O hEigeartaigh
>
> Need to get rid of deprecated DefaultHttpClient class references. Most, if 
> not all, occur in tests at this point since the Dispatch framework has 
> already moved on to the new classes and API from httpclient. 
> Besides cleaning up, the tests appear to have some erratic behavior on some 
> OS/jdk combinations with this deprecated class. These random test failures go 
> away when using the new classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (KNOX-454) NullPointerException thrown when JSON response expected but plain text recieved

2017-06-08 Thread Larry McCay (JIRA)


 [ 
https://issues.apache.org/jira/browse/KNOX-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay resolved KNOX-454.
--
Resolution: Incomplete

> NullPointerException thrown when JSON response expected but plain text 
> recieved
> ---
>
> Key: KNOX-454
> URL: https://issues.apache.org/jira/browse/KNOX-454
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.5.0
>Reporter: Kevin Minder
>Assignee: Kevin Minder
>Priority: Critical
> Fix For: Future
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (KNOX-454) NullPointerException thrown when JSON response expected but plain text recieved

2017-06-08 Thread Larry McCay (JIRA)


[ 
https://issues.apache.org/jira/browse/KNOX-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042583#comment-16042583
 ] 

Larry McCay commented on KNOX-454:
--

I agree [~coheigea].

> NullPointerException thrown when JSON response expected but plain text 
> recieved
> ---
>
> Key: KNOX-454
> URL: https://issues.apache.org/jira/browse/KNOX-454
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.5.0
>Reporter: Kevin Minder
>Assignee: Kevin Minder
>Priority: Critical
> Fix For: Future
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (KNOX-558) HttpClient connections are not always returned to the pool for HBase on Windows

2017-06-08 Thread Larry McCay (JIRA)


 [ 
https://issues.apache.org/jira/browse/KNOX-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay resolved KNOX-558.
--
Resolution: Fixed

> HttpClient connections are not always returned to the pool for HBase on 
> Windows
> ---
>
> Key: KNOX-558
> URL: https://issues.apache.org/jira/browse/KNOX-558
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.6.0
>Reporter: Kevin Minder
>Assignee: Kevin Minder
>Priority: Blocker
> Fix For: 0.6.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Groovy SSL configuration

2017-06-08 Thread larry mccay

Hi Colm -

See the Client Shell Quick Start section in the Users Guide:
http://knox.apache.org/books/knox-0-12-0/user-guide.html#Client+Quickstart

Steps #3 and #4 should be all you need to do.

HTH,

--larry

On Thu, Jun 8, 2017 at 6:40 AM, Colm O hEigeartaigh 
wrote:

> How do I specify the SSL truststore when using the 'bin/shell.jar'? All of
> the examples I can find don't seem to configure the truststore, yet I get
> the following error:
>
> javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
>
> Colm.
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>

Groovy SSL configuration

2017-06-08 Thread Colm O hEigeartaigh

How do I specify the SSL truststore when using the 'bin/shell.jar'? All of
the examples I can find don't seem to configure the truststore, yet I get
the following error:

javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target

Colm.


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

[jira] [Commented] (KNOX-558) HttpClient connections are not always returned to the pool for HBase on Windows

2017-06-08 Thread Colm O hEigeartaigh (JIRA)


[ 
https://issues.apache.org/jira/browse/KNOX-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042516#comment-16042516
 ] 

Colm O hEigeartaigh commented on KNOX-558:
--

It looks like this issue has been fixed and could be closed.

> HttpClient connections are not always returned to the pool for HBase on 
> Windows
> ---
>
> Key: KNOX-558
> URL: https://issues.apache.org/jira/browse/KNOX-558
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.6.0
>Reporter: Kevin Minder
>Assignee: Kevin Minder
>Priority: Blocker
> Fix For: 0.6.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (KNOX-454) NullPointerException thrown when JSON response expected but plain text recieved

2017-06-08 Thread Colm O hEigeartaigh (JIRA)


[ 
https://issues.apache.org/jira/browse/KNOX-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042518#comment-16042518
 ] 

Colm O hEigeartaigh commented on KNOX-454:
--

This issue could be marked as resolved IMO as there is not enough information 
to reproduce it.

> NullPointerException thrown when JSON response expected but plain text 
> recieved
> ---
>
> Key: KNOX-454
> URL: https://issues.apache.org/jira/browse/KNOX-454
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.5.0
>Reporter: Kevin Minder
>Assignee: Kevin Minder
>Priority: Critical
> Fix For: Future
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (KNOX-932) Option to remove the server-name from HTTP-header response

[jira] [Commented] (KNOX-932) Option to remove the server-name from HTTP-header response

[jira] [Commented] (KNOX-932) Option to remove the server-name from HTTP-header response

[jira] [Assigned] (KNOX-932) Option to remove the server-name from HTTP-header response

[jira] [Updated] (KNOX-932) Option to remove the server-name from HTTP-header response

[jira] [Created] (KNOX-965) SecureQueryDecryptProcessor decode call could return null thus it would get a NPE

[jira] [Updated] (KNOX-949) WeBHDFS proxy replaces %20 encoded spaces in URL with + encoding

[jira] [Assigned] (KNOX-949) WeBHDFS proxy replaces %20 encoded spaces in URL with + encoding

[jira] [Updated] (KNOX-759) jansi dependency causes issues starting knox shell

[jira] [Updated] (KNOX-759) jansi dependency causes issues starting knox shell

Re: Groovy SSL configuration

Re: Groovy SSL configuration

Re: [DISCUSS] Planning for Apache Knox 0.13.0 (1.0.0) Release

[jira] [Assigned] (KNOX-738) Remove references to deprecated httpclient class DefaultHttpClient

[jira] [Resolved] (KNOX-454) NullPointerException thrown when JSON response expected but plain text recieved

[jira] [Commented] (KNOX-454) NullPointerException thrown when JSON response expected but plain text recieved

[jira] [Resolved] (KNOX-558) HttpClient connections are not always returned to the pool for HBase on Windows

Re: Groovy SSL configuration

Groovy SSL configuration

[jira] [Commented] (KNOX-558) HttpClient connections are not always returned to the pool for HBase on Windows

[jira] [Commented] (KNOX-454) NullPointerException thrown when JSON response expected but plain text recieved

21 matches

Site Navigation

Mail list logo

Footer information