Skip to main content

HEAD request opening a TSBChannelStream unnecessarily

1 reply [Last post]
HEAD request opening a TSBChannelStream unnecessarily
February 13, 2012 - 08:19
ramks
Offline
Joined: 2010-06-17
Points: 0

In ChannelRequestInterceptor, TSBChannelStream is created even when a HEAD request is intercepted. The stream is stopped afterwards on seeing it is a HEAD request.

This is unnecessary. Especially because the inside TSBChannelStream constructor, tuning required to satisfy NetResourceUsage happens.

If a client just asks for HEAD request, it might result in Contention even though there isn't one required.

‹ https Displaying image on ocap ri ›

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Re: HEAD request opening a TSBChannelStream unnecessarily
February 13, 2012 - 16:18
#1
scottdeboy
Offline
Joined: 2009-02-02
Points: 0

Validation of the request parameters requires creation of a TSBChannelStream in order to determine the available content range and other fields.