Jump to content
UBot Underground

entroqy

Members
  • Content Count

    38
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by entroqy

  1. Looking for a link to the EULA that was displayed when the software was registered. Thanks
  2. >If you are putting up a Wall to prevent UBot So using Internet Explorer with a proxy that requires authentication is "putting up a UBot Wall". Because, that doesn't work for me either, and that has nothing to do with Squid. Slightly different problem, but also something that stops UBot from working. Sure, both can be worked around once the issue is known, but why should we have to? When you configure a proxy, there is always a reason for doing so. Why else would anyone go near IE? >I am thinking about moving this thread to the "General Discussion" area. Your perogative, yo
  3. The issue is not really a UBOT issue. It's Microsoft issue. Microsoft HTTP components by default do not play nice with HTTP1.0 proxies. There's a setting change that takes care of the issue. For me, it becomes a UBOT issue when UBOT will not run with that type of proxy configured. If I'm being unreasonable in that expectation, then educate me. If you decide this is not a UBOT problem, that's OK. Just say so out loud. Then we have a clear statement about the environment in which UBOT doesn't work. Save the next guy a bit of time. I understand that you get to make the rules, I have no probl
  4. Correction, works fine if the HTTP 1.1 proxy doesn't need authentication. If the proxy wants authentication, the startup doesn't seem to handle that.
  5. Works fine without squid, and works fine with HTTP1.1 proxies.
  6. I'm using IE with a Squid proxy. Starting UBOT brings up the error "The remote server returned an unexpected response: (417) Expectation failed." Steps to reproduce - 1. Configure IE to use a Squid proxy. (Last time I looked, Squid still does not support HTTP 1.1.) 2. Start UBOT 3. Error message "The remote server returned an unexpected response: (417) Expectation failed. (see attached image) 4. UBOT exits. This is a known Microsoft issue. One way to solve that works for me is to add the code below to the (WebClient/HTTPWebRequest/etc) setup: ServicePointManager.Expect100Continue = f
×
×
  • Create New...