Ok, I just booted fresh solr 4.10.2, started example-schemaless and hit http://localhost:8983/solr/collection1/schema/fields - and it worked.
So, I suspect the problem is not with Solr but with your setup around it. For example, is your Solr listening on port 9943 directly (and not 8983) or do you have a proxy in between. Maybe the proxy is not configured to forward that URL. Do you have logs? Can you see if that URL is actually being called on Solr's side? If you see other urls (like generic admin stuff), but not this one, then it may not be making it there. Regards, Alex. Personal: http://www.outerthoughts.com/ and @arafalov Solr resources and newsletter: http://www.solr-start.com/ and @solrstart Solr popularizers community: https://www.linkedin.com/groups?gid=6713853 On 6 November 2014 13:27, nbosecker <nbosec...@gmail.com> wrote: > Thanks for the reply! > > My Solr has 2 cores(collection1/collection2), I can access them via the Solr > dashboard with no problem. > https://myserver:9943/solr/#/collection1 > https://myserver:9943/solr/#/collection2 > > I can also verify the solrconfig.xml for them contain the schemaless config: > https://myserver:9943/solr/collection1/admin/file?file=solrconfig.xml&contentType=text/xml;charset=utf-8 > > I'm perplexed, as the managed_schema file has been created and seems to be > active, yet the API continue to give 404. Is this the correct format to > access? > https://myserver:9943/solr/collection1/schema/fields > > (I've also tried other variations, removing the collection name etc...always > 404). > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Schemaless-configuration-using-4-10-2-API-returning-404-tp4167869p4168028.html > Sent from the Solr - User mailing list archive at Nabble.com.
