Re: v2 API "Broader Changes" and Next Steps

2022-07-23 Thread Gus Heck
On Sat, Jul 23, 2022 at 1:38 PM Shawn Heisey wrote: > On 7/23/2022 9:41 AM, Gus Heck wrote: > > There is something of a risk to have a server that accepts non safe get > > requests. All these requests are contrary to the HTTP specification ( > > https://www.rfc-editor.org/rfc/rfc9110.html#section

Re: v2 API "Broader Changes" and Next Steps

2022-07-23 Thread Marcus Eagan
Really happy to see everyone's interest in supporting beginning users. I often feel protecting them is one really important aspect of supporting them. There is a mechanism for disabling the Admin API by default. In SOLR-14014 I added a flag for th

Re: v2 API "Broader Changes" and Next Steps

2022-07-23 Thread Shawn Heisey
On 7/23/2022 9:41 AM, Gus Heck wrote: There is something of a risk to have a server that accepts non safe get requests. All these requests are contrary to the HTTP specification ( https://www.rfc-editor.org/rfc/rfc9110.html#section-9.2.1). If the only way to make certain things happen with a GE

Re: v2 API "Broader Changes" and Next Steps

2022-07-23 Thread Gus Heck
Lost track of this convo for a while... but basically like what I read. I like that we've acknowledged the positive role of the UI, and I also very much like the use of http verbs for v2. The primary concern for me is that I can do most things via a browser connection to solr, so a kibana-like ui o