Created a custom handler and behaves as my title states, but I need parallel processing of requests. This handler asks to a second machine for html content, images and other web page related content. But as every request gets kind of "queued" the result is a very slow response of content. Web browsers are able to send multiple requests at the same time, but this "problem" reduces it to a single request.
I've verified this behavior logging the begging and ending of the handler. Never a request starts before the previous ends.
Also logged global.asax Application_BeginRequest event, and note that this event is called as fast as the request is received. The problem is somehow between the fire of this event and the invocation of my handler.
Any help would be really appreciate.