You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Anthony Webster <an...@transcendenz.co.uk> on 2011/06/20 13:26:45 UTC
Can't find the the request for http://localhost:9000/favicon.ico's
Observer ?
Hi,
I have a number of webservices running on an embedded Jetty server. This all
works fine. I can see the list of webservices at localhost:9000 and obtain a
wsdl for each via the URL localhost:9000/SomeService?wsdl. I can use the
services without any problem. However whenever I retrieve a service listing
or wsdl via a navigator I see the following warning message in the server
logs :
WARN: Can't find the the request for http://localhost:9000/favicon.ico'sObserver
This doesn't happen when consumming webservices normally through cxf
clients. Any ideas?
Thanks,
Anthony
RE: Can't find the the request for
http://localhost:9000/favicon.ico's Observer ?
Posted by Sven Zethelius <sv...@expedia.com>.
This is the result of the browser behavior. It's sending a request for /favicon.ico, which isn't understood since there isn't a handler. The browser ignores the error and continues with just the default icon. Some sites have a favicon, which allows bookmarks, etc. to be customized with the site's logo. You can ignore the error.
-----Original Message-----
From: awe.transcendenz@gmail.com [mailto:awe.transcendenz@gmail.com] On Behalf Of Anthony Webster
Sent: Monday, June 20, 2011 4:27 AM
To: users
Subject: Can't find the the request for http://localhost:9000/favicon.ico's Observer ?
Hi,
I have a number of webservices running on an embedded Jetty server. This all
works fine. I can see the list of webservices at localhost:9000 and obtain a
wsdl for each via the URL localhost:9000/SomeService?wsdl. I can use the
services without any problem. However whenever I retrieve a service listing
or wsdl via a navigator I see the following warning message in the server
logs :
WARN: Can't find the the request for http://localhost:9000/favicon.ico'sObserver
This doesn't happen when consumming webservices normally through cxf
clients. Any ideas?
Thanks,
Anthony