[jetty-users] BasicAuthenticator response in validateRequest hard coded

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jetty-users] BasicAuthenticator response in validateRequest hard coded

From: Shalmi Gawde-Naik <shalmi.naik@xxxxxxxxx>
Date: Fri, 12 Dec 2014 15:54:34 +0530
Delivered-to: jetty-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jetty-users>
List-help: <mailto:jetty-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=unsubscribe>

Hi,

The validateRequest method in BasicAuthenticator sets response header as "basic realm=\" which is hard coded string. Is this possible to configure this thing?

Also in most of the cases the response header is expected as "Basic" (B being capital) instead of "basic"(b being small). In early versions of jetty( I had used jetty 4 as embedded and now upgraded to jetty9 also as embedded server) this used to be "Basic". So some of the clients are failing because of this change. Is it possible to change this behavior?

Any suggestions/info on this are highly appreciated.

Thanks & regards

Shalmi Naik

Prev by Date: Re: [jetty-users] [jetty-dev] HTTP/2 support in Jetty 9.3.0
Next by Date: Re: [jetty-users] [jetty-dev] HTTP/2 support in Jetty 9.3.0
Previous by thread: [jetty-users] Preventing queuing of requests when all connections exhausted
Next by thread: [jetty-users] Persistent queue for rejected HTTP requests
Index(es):
- Date
- Thread

Breadcrumbs