I can not set Hostname property to IPv6 address using JK Status Manager

2014-06-12 Thread Hiroto Shimizu
Hi

I use mod_jk 1.2.40, httpd-2.2.15-29.el6.centos.x86_64.
In web browser Firefox, I set Hostname property to IPv6
address(2001:c0a8::1) using JK Status Manager, But error occured.

Is there a solution to the problem?

-mod_jk.log
[Thu Jun 12 11:09:13.029 2014] [4233:140197382711040] [info]
commit_member::jk_status.c (3369): Status worker 'jkstatus' setting 'host'
for sub worker 'ajp13w' to '2001%3Ac0a8%3A%3A1'
[Thu Jun 12 11:09:13.029 2014] [4233:140197382711040] [error]
commit_member::jk_status.c (3384): Status worker 'jkstatus' failed
resolving address '2001%3Ac0a8%3A%3A1:8009' for sub worker 'ajp13w'.
-


Re: I can not set Hostname property to IPv6 address using JK Status Manager

2014-06-12 Thread Konstantin Kolinko
2014-06-12 13:34 GMT+04:00 Hiroto Shimizu shimizuhiroto...@gmail.com:
 Hi

 I use mod_jk 1.2.40, httpd-2.2.15-29.el6.centos.x86_64.
 In web browser Firefox, I set Hostname property to IPv6
 address(2001:c0a8::1) using JK Status Manager, But error occured.

 Is there a solution to the problem?

 -mod_jk.log
 [Thu Jun 12 11:09:13.029 2014] [4233:140197382711040] [info]
 commit_member::jk_status.c (3369): Status worker 'jkstatus' setting 'host'
 for sub worker 'ajp13w' to '2001%3Ac0a8%3A%3A1'
 [Thu Jun 12 11:09:13.029 2014] [4233:140197382711040] [error]
 commit_member::jk_status.c (3384): Status worker 'jkstatus' failed
 resolving address '2001%3Ac0a8%3A%3A1:8009' for sub worker 'ajp13w'.
 -

Please create an issue in Bugzilla. It would be better to include a
step-by-step recipe to reproduce the issue.

There were some fixes to jk_resolve, but in your case the problem is
that url-encoded parameter value (2001%3Ac0a8%3A%3A1) is passed as
is to the jk_resolve method.

Looking at the code, jk_status.c has its own HTTP query parameters
parsing (status_parse_uri() in native/common/jk_status.c), implemented
by splitting the query string.
The url-decoding of parameters is not performed. There is a comment
that it had been planned, but has not been implemented yet.

/* XXX Depending on the params values, we might need to trim and decode */


Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: I can not set Hostname property to IPv6 address using JK Status Manager

2014-06-12 Thread Hiroto Shimizu
Konstantin

Thank you for your reply.
I created an issue in Bugzilla.

https://issues.apache.org/bugzilla/show_bug.cgi?id=56618

 The url-decoding of parameters is not performed. There is a comment
 that it had been planned, but has not been implemented yet.

  /* XXX Depending on the params values, we might need to trim and decode
*/
Thank you for telling me about the problem.


2014-06-12 19:02 GMT+09:00 Konstantin Kolinko knst.koli...@gmail.com:

 2014-06-12 13:34 GMT+04:00 Hiroto Shimizu shimizuhiroto...@gmail.com:
  Hi
 
  I use mod_jk 1.2.40, httpd-2.2.15-29.el6.centos.x86_64.
  In web browser Firefox, I set Hostname property to IPv6
  address(2001:c0a8::1) using JK Status Manager, But error occured.
 
  Is there a solution to the problem?
 
  -mod_jk.log
  [Thu Jun 12 11:09:13.029 2014] [4233:140197382711040] [info]
  commit_member::jk_status.c (3369): Status worker 'jkstatus' setting
 'host'
  for sub worker 'ajp13w' to '2001%3Ac0a8%3A%3A1'
  [Thu Jun 12 11:09:13.029 2014] [4233:140197382711040] [error]
  commit_member::jk_status.c (3384): Status worker 'jkstatus' failed
  resolving address '2001%3Ac0a8%3A%3A1:8009' for sub worker 'ajp13w'.
  -

 Please create an issue in Bugzilla. It would be better to include a
 step-by-step recipe to reproduce the issue.

 There were some fixes to jk_resolve, but in your case the problem is
 that url-encoded parameter value (2001%3Ac0a8%3A%3A1) is passed as
 is to the jk_resolve method.

 Looking at the code, jk_status.c has its own HTTP query parameters
 parsing (status_parse_uri() in native/common/jk_status.c), implemented
 by splitting the query string.
 The url-decoding of parameters is not performed. There is a comment
 that it had been planned, but has not been implemented yet.

 /* XXX Depending on the params values, we might need to trim and decode */


 Best regards,
 Konstantin Kolinko

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org