Last post Jun 08, 2006 05:25 PM by aosipov
Jun 06, 2006 04:50 PM|aosipov|LINK
It seems to me that secure sites running the batching request manager are routed via https to the atlasbatchcall.axd then subsequent requests distrubuted by MultiRequestHandler are called via http protocol (or at least emulated to see that way).
Seems to be a bug. I expect this mechanism to use whatever the protocol that atlasbatchcall.axd was opened with and all the batched calls should be called with the same protocol. Can someone chime in on this?
Jun 08, 2006 04:58 PM|HaoK|LINK
Thanks for the feedback, we will consider making this change in the future (to respect the protocol of the original request when handling batched requests)
Jun 08, 2006 05:07 PM|aosipov|LINK
Just some more comments. I have not spent any time looking at how the requests are handled: either internally or actual requests. If actual requests are used it would be fairly impossible to simulate an exact https request (because of certificate). Maybe
you can comment on this. If this is the case is there anyway I can find out if the request was batched?
Jun 08, 2006 05:13 PM|HaoK|LINK
Unfortunately, in the current bits I don't think there's a great non ugly way to tell if the request is batched child request or not. You might be able to play tricks if you want to look at what the HttpHandler is for the request, but that's a pretty fragile
solution. We will look into making this much easier in the future though...
Hope that helps,
Jun 08, 2006 05:25 PM|aosipov|LINK
Thanks. Not a big problem at the moment since everything works without batching. My solution is even uglier, I noticed the url is an ip address, any request to secure site would not be accessible via ip address because of the certificate name.