You are completely right. It seems that the message is malformed. It is missing the /solr path prefix (for V1 API), or /api/collections path prefix (for V2 API). To fix it simply provide a custom solr URL like below:
bin/solr config -c mysearchindex -solrUrl http://localhost:8983/api/collections -action set-user-property -property update.autoCreateFields -value false I tested the above with 9.6.1. I will file a ticket for this as well. On Tue, Sep 24, 2024 at 3:01 PM Ehrenleitner Robert Harald < robert.ehrenleit...@plus.ac.at> wrote: > Once again, to be sure: > > $ searchIndex=mysearchindex > $ bin/solr create -c $searchIndex > WARNING: Using _default configset with data driven schema functionality. > NOT RECOMMENDED for production use. > To turn off: bin/solr config -c mysearchindex -p 8983 -action > set-user-property -property update.autoCreateFields -value false > > Created new core 'mysearchindex' > $ bin/solr config -c mysearchindex -p 8983 -action set-user-property > -property update.autoCreateFields -value false > Neither -zkHost or -solrUrl parameters provided so assuming solrUrl is > http://localhost:8983. > > POSTing request to Config API: http://localhost:8983/mysearchindex/config > {"set-user-property":{"update.autoCreateFields":"false"}} > > ERROR: Error from server at > http://localhost:8983/mysearchindex/config?wt=javabin&version=2: Expected > mime type in [application/vnd.apache.solr.javabin, > application/octet-stream] but got text/html. <html> > <head> > <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/> > <title>Error 404 Not Found</title> > </head> > <body><h2>HTTP ERROR 404 Not Found</h2> > <table> > <tr><th>URI:</th><td>/mysearchindex/config</td></tr> > <tr><th>STATUS:</th><td>404</td></tr> > <tr><th>MESSAGE:</th><td>Not Found</td></tr> > <tr><th>SERVLET:</th><td>-</td></tr> > </table> > > </body> > </html> > > > In the command "bin/solr config", the variable "$searchIndex" is not used, > because the whole command is copied-pasted from the output above. > >
