# Resetting to start of TransportClient request's input stream?

**URL:** <https://discuss.elastic.co/t/resetting-to-start-of-transportclient-requests-input-stream/8996>\
**Category:** Elasticsearch\
**Created:** [September 11, 2012, 6:52pm UTC](https://discuss.elastic.co/t/resetting-to-start-of-transportclient-requests-input-stream/8996 "2012-09-11T18:52:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\
**Post date:** [September 11, 2012, 6:52pm UTC](https://discuss.elastic.co/t/resetting-to-start-of-transportclient-requests-input-stream/8996/1 "2012-09-11T18:52:48Z")

</div>

Hello,

If I want to intercept a TransportClient request, look inside of it (e.g.,  
to check what type of a call this is), and then pass on/forward the  
whole/original TransportClient request, how can I do that?

It seems that one can't read the request a little bit and then reset/rewind  
back to the beginning of the input stream. Is there any way around that?  
Should we open a ticket and provide a patch? Or is resetting back to the  
beginning of the input stream simply not doable?

## Thanks, Otis

Search Analytics - [http://sematext.com/search-analytics/index.html](http://sematext.com/search-analytics/index.html)  
Performance Monitoring - [http://sematext.com/spm/index.html](http://sematext.com/spm/index.html)

--

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:13am UTC](https://discuss.elastic.co/t/resetting-to-start-of-transportclient-requests-input-stream/8996/2 "2017-07-06T03:13:07Z")

</div>

Closed on July 6, 2017, 3:13am UTC