"no default request handler is registered (either '/select' or 'standard')"

I'm doing some experimenting with Solr 5.3 and the 7.x-1.x-dev version of the Apache Solr Search module. I copied the configuration files from http://cgit.drupalcode.org/sandbox-cpliakas-1600962/tree/conf/5.x and things seem to be working fine, except that this warning message appears in the Solr admin logging window:

no default request handler is registered (either '/select' or 'standard')

Looking at solrconfig.xml, I see a requestHandler named "standard". I also see a handler named pinkPony with a "default attribute set to "true". So it seems like there is indeed a default requestHandler specified. So why might the warning appear?

I asked this same question on the solr-user@lucene.apache.org mailing list and got these replies:

Thats... strange.

Looking at hte code it appears to be a totally bogus and missleading 
warning -- but it also shouldn't affect anything.

You can feel free to ignore it for now...

https://issues.apache.org/jira/browse/SOLR-7984

I think the warning message may be misworded, or logged in incorrect
circumstances, and might need some attention.

The solrconfig.xml that you are using (which I assume came from the
Drupal project) is geared towards a 3.x version of Solr prior to 3.6.x
(the last minor version in the 3.x line).

Starting in the 3.6 version, all request handlers in examples have names
that start with a forward slash, like "/select", none of them have the
"default" attribute, and the handleSelect parameter found elsewhere in
the solrconfig.xml is false.

You should bring this up with the Drupal folks and ask them to upgrade
their config/schema and their code for modern versions of Solr.  Solr
3.6.0 (which deprecated their handler naming convention and the
"default" attribute) was released over three years ago.

More info than you probably wanted to know:  The reason this change was
made is security-related.  With the old way of naming request handlers
and handling /select indirectly, you could send a query to /select,
include a qt=/update parameter, and change the index via a handler
intended only for queries.

I just want to clarify: all of Shawn's points below are valid and good -- 
but they stll don't explain the warning messgae you are getting.  it makes 
no sense as the code is currently written, and doesn't do anything to help 
encourage people to transition to path based handler names.