Hi Everyone,
we've decided it'd be best to open a new thread in order to do some consolidation work on the HTTP Proxy issues which have been popping up at least since 8.940. Note that the below listed threads will therefore be closed finally:
So for anything related to those two issues please make sure you post in this thread; we'll also give any further information in this thread only.
However for this attempt we need your help to perform further debugging and to be able to fix the problems after all. What do we like you to do now, then?
And of course don't forget to name the exact build version you're running on your system.
I know that this will require quite a lot of work, but without your committing help we're not able to fathom the causes for the issues.
If you require any of the logs to remain confidentially, I'd like you to send them to me via PM; they'll only be used for debugging purposes internally and will therefore be treated absolutely confidential (only the developer team will have access to them).
We'll only deal with constructive replies and we'd therefore like you to distance yourself from any non related issues here and urge you to provide us with any other details and information you consider useful. We may also request further help in due time.
Thanks for your help and understanding.
Cheers,
Cristof
we've decided it'd be best to open a new thread in order to do some consolidation work on the HTTP Proxy issues which have been popping up at least since 8.940. Note that the below listed threads will therefore be closed finally:
So for anything related to those two issues please make sure you post in this thread; we'll also give any further information in this thread only.
However for this attempt we need your help to perform further debugging and to be able to fix the problems after all. What do we like you to do now, then?
- make use of FireBug (Firefox developer plugin) to see what concrete URL causes your "Timeouts" or "Broken pipes" and/or
- see if you can pin down an URL which constantly reproduces the issue (or maybe both at once) via this plugin,
- make use of WireShark to produce a pcap file of a whole sessions' communication,
- make sure you can prove your findings by means of the whole logfile or logfile snippets,
- give our developer team access to your affected UTM(s) for final debugging,
- stay focused, commited and on topic even if it can be chewy once in a while.
And of course don't forget to name the exact build version you're running on your system.
I know that this will require quite a lot of work, but without your committing help we're not able to fathom the causes for the issues.
If you require any of the logs to remain confidentially, I'd like you to send them to me via PM; they'll only be used for debugging purposes internally and will therefore be treated absolutely confidential (only the developer team will have access to them).
We'll only deal with constructive replies and we'd therefore like you to distance yourself from any non related issues here and urge you to provide us with any other details and information you consider useful. We may also request further help in due time.
Thanks for your help and understanding.
Cheers,
Cristof