Unfortunately I could not replicate your success :-( Let me show you what I did in case you may be notice any difference from your case.
<https://lh6.googleusercontent.com/-HzQRKhGl9ag/VMqfkWnSF8I/AAAAAAAAAh0/SsXrJlQ2vW8/s1600/Output_Caching.png> <https://lh6.googleusercontent.com/-V2VTx-iT888/VMqf0K7jChI/AAAAAAAAAh8/qC7umA0XP_U/s1600/AppPool1.png> <https://lh6.googleusercontent.com/-4jL3Hyoq0QY/VMqgF7d0-II/AAAAAAAAAiE/77VOeAZP2e0/s1600/AppPool2.png> <https://lh5.googleusercontent.com/-aBFCh_BZKn4/VMqgnM9ejhI/AAAAAAAAAiM/zxnsdD-VK8U/s1600/Error.png> Any ideas what I may be missing? Thanks! Konstantin On Thursday, January 29, 2015 at 10:13:40 AM UTC-8, Cijo Thomas wrote: > > I have been fighting with this for quite some time, Finally found the > workaround. Let me know if it helps you! > > On Thu, Jan 29, 2015 at 10:12 AM, Konstantin Erman <kon...@gmail.com > <javascript:>> wrote: > >> Thank you for the good news! I'm a little swamped currently, but I will >> definitely give it a try when I get a minute. >> >> Just to make sure - "disable Output cache for the website" - where is it >> in IIS Management Console? >> >> >> On Wednesday, January 28, 2015 at 4:38:01 PM UTC-8, Cijo Thomas wrote: >>> >>> Its possible to use IIS with the following steps. >>> 1) Disable Output cache for the website you are using as reverse proxy. >>> 2) Run the website in a new apppool, which do not have any managed code. >>> >>> With the above two steps, kibana4 runs fine with IIS as reverse proxy. >>> >>> >>> On Saturday, December 27, 2014 at 4:19:31 PM UTC-8, Konstantin Erman >>> wrote: >>>> >>>> We currently use Kibana 3 hosted in IIS behind IIS reverse proxy for >>>> auhentication. Naturally we look at Kibana 4 Beta 3 expecting it to >>>> replace >>>> Kibana 3 soon. Kibana 4 is self hosted and works nicely when accessed >>>> directly, but we need authentication and whatever I do I cannot make it >>>> work from behind reverse proxy! Early or later I get 401 accessing some >>>> internal resource. >>>> >>>> Wonder if anybody hit similar problem and have any insight how to make >>>> it work. >>>> We cannot use Shield as its price is way beyond our bounds. >>>> >>>> Thanks! >>>> Konstantin >>> >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "elasticsearch" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/elasticsearch/r_uDcHR-rrw/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> elasticsearc...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/d089ed71-71c4-4997-93fa-2dc7125b7f49%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/d089ed71-71c4-4997-93fa-2dc7125b7f49%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Warm Regards, > Cijo Thomas > +1 3125606441 > <#CAH6LTpEkRjF1kDbKEm5Frvwb6BBCH_Xhvm1hhKtMYtYCphrraQ@mail.gmail.com_SafeHtmlFilter_> > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/cbf5e8d0-6769-4ef5-b625-9a6457fac86c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
