I started having issues today connecting to forum.dlang.org from
the proxy server we use at work (I work at HP). I've never had
this problem before today.  I can connect if I use a 3rd party
proxy server (such as https://hide.me/en/proxy).  I captured a
wireshark trace and I'm just not getting any response from the
initial HTTP request.  I get the ACK from the request but never
get any response.  I've been trying it all day and it hasn't
worked.

I first tried using different proxy servers and it seems that all
the HP proxy servers aren't working. So, my best guess is that
the forum.dlang.org server might be blocking or limiting packets
from ip addresses it gets too many requests from.

We have a variety of proxies we can use to connect outside our
private network, I've tried three of them and they all can't
connect.  Here's there host names and ip addresses:

1. proxy-txn.austin.hp.com (16.85.175.70)
2. proxy.houston.hp.com (16.85.88.10)
3. web-proxy.corp.hp.com (16.85.175.150)

I don't know who manages the dlang servers, but if someone sees
this could you grep the logs/error logs for these ip addresses
and see if they are being blocked in some way?  There are alot of
machines behind these ip addresses so maybe the server thinks it
might be getting DOS'd from these ip addresses, when in reality,
it's just alot of machines using these ip addresses as proxy
connections.

Thanks.

P.S.  I didn't post this using my regular login because I don't
want to login through the 3rd party proxy server I'm connecting
through.

On Tuesday, 11 November 2014 at 00:59:59 UTC, Jonathan Marler wrote:
> I started having issues today connecting to forum.dlang.org from
> the proxy server we use at work (I work at HP). I've never had
> this problem before today.  I can connect if I use a 3rd party
> proxy server (such as https://hide.me/en/proxy).  I captured a
> wireshark trace and I'm just not getting any response from the
> initial HTTP request.  I get the ACK from the request but never
> get any response.  I've been trying it all day and it hasn't
> worked.
>
> I first tried using different proxy servers and it seems that all
> the HP proxy servers aren't working. So, my best guess is that
> the forum.dlang.org server might be blocking or limiting packets
> from ip addresses it gets too many requests from.
>
> We have a variety of proxies we can use to connect outside our
> private network, I've tried three of them and they all can't
> connect.  Here's there host names and ip addresses:
>
> 1. proxy-txn.austin.hp.com (16.85.175.70)
> 2. proxy.houston.hp.com (16.85.88.10)
> 3. web-proxy.corp.hp.com (16.85.175.150)
>
> I don't know who manages the dlang servers, but if someone sees
> this could you grep the logs/error logs for these ip addresses
> and see if they are being blocked in some way?  There are alot of
> machines behind these ip addresses so maybe the server thinks it
> might be getting DOS'd from these ip addresses, when in reality,
> it's just alot of machines using these ip addresses as proxy
> connections.
>
> Thanks.
>
> P.S.  I didn't post this using my regular login because I don't
> want to login through the 3rd party proxy server I'm connecting
> through.

I'm still having this issue, this is quite an annoyance.  Can
someone tell me who to contact for this?  Feel free to send me an
email at johnnymarler@gmail.com

I'm looking to talk to whoever manages the dlang servers.  This
problem occurs on forum.dlang.org and wiki.dlang.org, it does not
happen when connecting to dlang.org

Thanks.

On Tuesday, 11 November 2014 at 18:50:15 UTC, Jonathan Marler wrote:

> I'm still having this issue, this is quite an annoyance.

I also have issues with with https://, but with http:// it works fine.

Mike

On Tuesday, 11 November 2014 at 18:50:15 UTC, Jonathan Marler wrote:
> On Tuesday, 11 November 2014 at 00:59:59 UTC, Jonathan Marler wrote:
>> I started having issues today connecting to forum.dlang.org from
>> the proxy server we use at work (I work at HP). I've never had
>> this problem before today.  I can connect if I use a 3rd party
>> proxy server (such as https://hide.me/en/proxy).  I captured a
>> wireshark trace and I'm just not getting any response from the
>> initial HTTP request.  I get the ACK from the request but never
>> get any response.  I've been trying it all day and it hasn't
>> worked.
>>
>> I first tried using different proxy servers and it seems that all
>> the HP proxy servers aren't working. So, my best guess is that
>> the forum.dlang.org server might be blocking or limiting packets
>> from ip addresses it gets too many requests from.
>>
>> We have a variety of proxies we can use to connect outside our
>> private network, I've tried three of them and they all can't
>> connect.  Here's there host names and ip addresses:
>>
>> 1. proxy-txn.austin.hp.com (16.85.175.70)
>> 2. proxy.houston.hp.com (16.85.88.10)
>> 3. web-proxy.corp.hp.com (16.85.175.150)
>>
>> I don't know who manages the dlang servers, but if someone sees
>> this could you grep the logs/error logs for these ip addresses
>> and see if they are being blocked in some way?  There are alot of
>> machines behind these ip addresses so maybe the server thinks it
>> might be getting DOS'd from these ip addresses, when in reality,
>> it's just alot of machines using these ip addresses as proxy
>> connections.
>>
>> Thanks.
>>
>> P.S.  I didn't post this using my regular login because I don't
>> want to login through the 3rd party proxy server I'm connecting
>> through.
>
> I'm still having this issue, this is quite an annoyance.  Can
> someone tell me who to contact for this?  Feel free to send me an
> email at johnnymarler@gmail.com
>
> I'm looking to talk to whoever manages the dlang servers.  This
> problem occurs on forum.dlang.org and wiki.dlang.org, it does not
> happen when connecting to dlang.org

That would be Vladimir Panteleev <vladimir@thecybershadow.net>.

As I understand, HTTP proxies work at the application layer: if the target site refuses connection, they report it to the client as such, sometimes even with a custom page. I'd say, wireshark diagnoses the proxy itself, not the target site.