Kibana not loading graphs

Hi,

I am working in setting up Kibana and processing the requests through elastic security plugin: https://github.com/salyh/elasticsearch-security-plugin. When the plug in is enabled, I get the following response for OPTIONS query.

Fiddler trace for Input:
OPTIONS http://myservername:9200/myindex/_search HTTP/1.1
Host: myservername:9200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Origin: http:// myservername:8080
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache

Fiddler trace for output:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Access-Control-Allow-Origin: *
Access-Control-Max-Age: 1728000
Access-Control-Allow-Methods: OPTIONS, HEAD, GET, POST, PUT, DELETE
Access-Control-Allow-Headers: X-Requested-With
Content-Type: application/json;charset=UTF-8
Content-Length: 2
Date: Mon, 27 Jan 2014 19:38:38 GMT

{}

When there is not Content, it is returning an empty byte array. In this scecnario, Kibana is not making any subsequent calls as it is expecting the 'Content-Length: 0'. Is there any way I can make Kibana load graphs by making subsequent class even if the returned content is NOT empty for OPTIONS request?

Thank you,

Ram Kotamaraja | Solutions Architect, DMBI
P: (617) 728-0595 | ext: 270595 M: (339) 368-1181
Ram.Kotamaraja@Altisource.commailto:Ram.Kotamaraja@Altisource.com


This email message and any attachments are intended solely for the use of the addressee. If you are not the intended recipient, you are prohibited from reading, disclosing, reproducing, distributing, disseminating or otherwise using this transmission. If you have received this message in error, please promptly notify the sender by reply email and immediately delete this message from your system. This message and any attachments may contain information that is confidential, privileged or exempt from disclosure. Delivery of this message to any person other than the intended recipient is not intended to waive any right or privilege. Message transmission is not guaranteed to be secure or free of software viruses.


--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/C4DEA6B73074194CB0BA02FC8CE731D02A24C121%40NAV8EMDAGP03.ASCORP.COM.
For more options, visit https://groups.google.com/groups/opt_out.

shoud be fixed with the following commits

Thank you Ram for your contributions

KR
Hendrik

Am Montag, 27. Januar 2014 20:47:06 UTC+1 schrieb Kotamaraja, Ram:

Hi,

I am working in setting up Kibana and processing the requests through
elastic security plugin:
GitHub - salyh/elasticsearch-security-plugin: Kerberos, LDAP, Active Directory, PKI/SSL/TLS and host/ip based ACL coarse-grained and document level security for elasticsearch (Authentication, Authorization, Auth, Spnego, ACL, Mutual authentication). When the plug in
is enabled, I get the following response for OPTIONS query.

Fiddler trace for Input:

OPTIONS http://myservername:9200/myindex/_search HTTP/1.1

Host: myservername:9200

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101
Firefox/26.0

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8

Accept-Language: en-US,en;q=0.5

Accept-Encoding: gzip, deflate

Origin: http:// myservername:8080

Access-Control-Request-Method: POST

Access-Control-Request-Headers: content-type

Connection: keep-alive

Pragma: no-cache

Cache-Control: no-cache

Fiddler trace for output:

HTTP/1.1 200 OK

Server: Apache-Coyote/1.1

Access-Control-Allow-Origin: *

Access-Control-Max-Age: 1728000

Access-Control-Allow-Methods: OPTIONS, HEAD, GET, POST, PUT, DELETE

Access-Control-Allow-Headers: X-Requested-With

Content-Type: application/json;charset=UTF-8

Content-Length: 2

Date: Mon, 27 Jan 2014 19:38:38 GMT

{}

When there is not Content, it is returning an empty byte array. In this
scecnario, Kibana is not making any subsequent calls as it is expecting the
'Content-Length: 0'. Is there any way I can make Kibana load graphs by
making subsequent class even if the returned content is NOT empty for
OPTIONS request?

Thank you,

--

Ram Kotamaraja | Solutions Architect, DMBI

P: (617) 728-0595 | ext: 270595 M: (339) 368-1181

Ram.Kot...@Altisource.com <javascript:>


This email message and any attachments are intended solely for the use of
the addressee. If you are not the intended recipient, you are prohibited
from reading, disclosing, reproducing, distributing, disseminating or
otherwise using this transmission. If you have received this message in
error, please promptly notify the sender by reply email and immediately
delete this message from your system.
This message and any attachments may contain information that is
confidential, privileged or exempt from disclosure. Delivery of this
message to any person other than the intended recipient is not intended to
waive any right or privilege. Message transmission is not guaranteed to be
secure or free of software viruses.


--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9f70b07a-a33b-4cef-9ed3-5eb026cc7d56%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hendrik,

Thanks for the email. I am glad I am able to contribute. I will start testing the DSL part and there might more feedback coming your way.

Thank you,

Ram Kotamaraja | Solutions Architect, DMBI
P: (617) 728-0595 | ext: 270595 M: (339) 368-1181
Ram.Kotamaraja@Altisource.commailto:Ram.Kotamaraja@Altisource.com

From: Hendrik [mailto:h.j.saly@googlemail.com]
Sent: Monday, February 03, 2014 7:53 AM
To: elasticsearch@googlegroups.com
Cc: Kotamaraja, Ram
Subject: Re: Kibana not loading graphs

shoud be fixed with the following commits



Thank you Ram for your contributions

KR
Hendrik

Am Montag, 27. Januar 2014 20:47:06 UTC+1 schrieb Kotamaraja, Ram:
Hi,

I am working in setting up Kibana and processing the requests through elastic security plugin: https://github.com/salyh/elasticsearch-security-plugin. When the plug in is enabled, I get the following response for OPTIONS query.

Fiddler trace for Input:
OPTIONS http://myservername:9200/myindex/_search HTTP/1.1
Host: myservername:9200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Origin: http:// myservername:8080
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache

Fiddler trace for output:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Access-Control-Allow-Origin: *
Access-Control-Max-Age: 1728000
Access-Control-Allow-Methods: OPTIONS, HEAD, GET, POST, PUT, DELETE
Access-Control-Allow-Headers: X-Requested-With
Content-Type: application/json;charset=UTF-8
Content-Length: 2
Date: Mon, 27 Jan 2014 19:38:38 GMT

{}

When there is not Content, it is returning an empty byte array. In this scecnario, Kibana is not making any subsequent calls as it is expecting the 'Content-Length: 0'. Is there any way I can make Kibana load graphs by making subsequent class even if the returned content is NOT empty for OPTIONS request?

Thank you,

Ram Kotamaraja | Solutions Architect, DMBI
P: (617) 728-0595 | ext: 270595 M: (339) 368-1181
Ram.Kot...@Altisource.com<javascript:>


This email message and any attachments are intended solely for the use of the addressee. If you are not the intended recipient, you are prohibited from reading, disclosing, reproducing, distributing, disseminating or otherwise using this transmission. If you have received this message in error, please promptly notify the sender by reply email and immediately delete this message from your system.
This message and any attachments may contain information that is confidential, privileged or exempt from disclosure. Delivery of this message to any person other than the intended recipient is not intended to waive any right or privilege. Message transmission is not guaranteed to be secure or free of software viruses.



This email message and any attachments are intended solely for the use of the addressee. If you are not the intended recipient, you are prohibited from reading, disclosing, reproducing, distributing, disseminating or otherwise using this transmission. If you have received this message in error, please promptly notify the sender by reply email and immediately delete this message from your system. This message and any attachments may contain information that is confidential, privileged or exempt from disclosure. Delivery of this message to any person other than the intended recipient is not intended to waive any right or privilege. Message transmission is not guaranteed to be secure or free of software viruses.


--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/C4DEA6B73074194CB0BA02FC8CE731D02A24E9C3%40NAV8EMDAGP03.ASCORP.COM.
For more options, visit https://groups.google.com/groups/opt_out.

great, i like to hear from you who its going ..


E-Mail: hendrik.saly@gmx.de
h.j.saly@googlemail.com
info@saly.de

PGP 0x22d7f6ec __________________ http://www.saly.de

2014-02-03 Kotamaraja, Ram Ram.Kotamaraja@altisource.com:

Hendrik,

Thanks for the email. I am glad I am able to contribute. I will start
testing the DSL part and there might more feedback coming your way.

Thank you,

--

Ram Kotamaraja | Solutions Architect, DMBI

P: (617) 728-0595 | ext: 270595 M: (339) 368-1181

Ram.Kotamaraja@Altisource.com

From: Hendrik [mailto:h.j.saly@googlemail.com]
Sent: Monday, February 03, 2014 7:53 AM
To: elasticsearch@googlegroups.com
Cc: Kotamaraja, Ram
Subject: Re: Kibana not loading graphs

shoud be fixed with the following commits

merged some stuff from pull request #1 · salyh/elasticsearch-security-plugin@8301b02 · GitHub

strict mode introduced, es+waffle+tomcat versions upgraded, some mino… · salyh/elasticsearch-security-plugin@212c9fa · GitHub

fixed classcastexception · salyh/elasticsearch-security-plugin@98e7980 · GitHub

Thank you Ram for your contributions

KR

Hendrik

Am Montag, 27. Januar 2014 20:47:06 UTC+1 schrieb Kotamaraja, Ram:

Hi,

I am working in setting up Kibana and processing the requests through
elastic security plugin:
GitHub - salyh/elasticsearch-security-plugin: Kerberos, LDAP, Active Directory, PKI/SSL/TLS and host/ip based ACL coarse-grained and document level security for elasticsearch (Authentication, Authorization, Auth, Spnego, ACL, Mutual authentication). When the plug in is
enabled, I get the following response for OPTIONS query.

Fiddler trace for Input:

OPTIONS http://myservername:9200/myindex/_search HTTP/1.1

Host: myservername:9200

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101
Firefox/26.0

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8

Accept-Language: en-US,en;q=0.5

Accept-Encoding: gzip, deflate

Origin: http:// myservername:8080

Access-Control-Request-Method: POST

Access-Control-Request-Headers: content-type

Connection: keep-alive

Pragma: no-cache

Cache-Control: no-cache

Fiddler trace for output:

HTTP/1.1 200 OK

Server: Apache-Coyote/1.1

Access-Control-Allow-Origin: *

Access-Control-Max-Age: 1728000

Access-Control-Allow-Methods: OPTIONS, HEAD, GET, POST, PUT, DELETE

Access-Control-Allow-Headers: X-Requested-With

Content-Type: application/json;charset=UTF-8

Content-Length: 2

Date: Mon, 27 Jan 2014 19:38:38 GMT

{}

When there is not Content, it is returning an empty byte array. In this
scecnario, Kibana is not making any subsequent calls as it is expecting the
'Content-Length: 0'. Is there any way I can make Kibana load graphs by
making subsequent class even if the returned content is NOT empty for
OPTIONS request?

Thank you,

--

Ram Kotamaraja | Solutions Architect, DMBI

P: (617) 728-0595 | ext: 270595 M: (339) 368-1181

Ram.Kot...@Altisource.com


This email message and any attachments are intended solely for the use of
the addressee. If you are not the intended recipient, you are prohibited
from reading, disclosing, reproducing, distributing, disseminating or
otherwise using this transmission. If you have received this message in
error, please promptly notify the sender by reply email and immediately
delete this message from your system.

This message and any attachments may contain information that is
confidential, privileged or exempt from disclosure. Delivery of this message
to any person other than the intended recipient is not intended to waive any
right or privilege. Message transmission is not guaranteed to be secure or
free of software viruses.



This email message and any attachments are intended solely for the use of
the addressee. If you are not the intended recipient, you are prohibited
from reading, disclosing, reproducing, distributing, disseminating or
otherwise using this transmission. If you have received this message in
error, please promptly notify the sender by reply email and immediately
delete this message from your system.

This message and any attachments may contain information that is
confidential, privileged or exempt from disclosure. Delivery of this message
to any person other than the intended recipient is not intended to waive any
right or privilege. Message transmission is not guaranteed to be secure or
free of software viruses.


--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAL6rNZwCppiQMnaLxDikjNToGVjcK16gSjPV9r%2BMTwd8ctfkmA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.