Re: 403 errors from www.w3.org/*

Denis,

That request is unknown to me, it seems to have come from a phone whose model is “CINK PEAK 2”, whose locale is set to “es_ES” (Spain). This does not match any phone in the house. We did have a house guest with WiFi access, but that was over a month ago, and before that no-one else since before Christmas. Our WiFi is WPA2-secured and we are very rural so I doubt anyone else has been using it. The other possibility is that the IP address is shared by my IP to other of his subscribers. I thought he had granted me our own fixed IP, so I’l check that side further.

In the meantime I shall await the un-ban.

Thanks again for your time.

> On 29 Mar 2017, at 08:06, Denis Ah-Kang <denis@w3.org> wrote:
> 
> Ok, looking more into the logs, it seems your IP has been blocked
> because we have detected a strange request coming from a phone
> (Dalvik/1.6.0 (Linux; U; Android 4.1.2; CINK PEAX 2 Build/JZO54K)).
> Here's the request, we received:
> [[
> POST
> /?auth_ver=2&appkey=8d661bff10da05e1316b4a86&nonce=1490614594870&is=214075540546933&model=CINK+PEAX+2&op=27202&signmd5=621993305&vendor=WIKO&locale=es_ES&pkg=com.trustgo.mobile.security&tk=Y1zIzz4VR9PJ4CCMCwZQOA%3D%3D&vn=2.3.0&h=960&w=540&v=462&ntt=WIFI&ie=862255020915960&lc=Z0MLSacBqvcbixHR&dpi=240&sdk=16&checkStr=f60024f804116feca35e620792ff474f&s=8ef3eacaf367047188fdba202dfd706b
> ]]
> 
> Any chance you know how this request was submitted?
> 
> Anyhow, the ban should be automatically removed after some times. Let
> me know if you still get these 403.
> 
> Regards,
> 
> Denis
> 
> 
> On 03/28/2017 06:29 PM, jalanb wrote:
>> Hi Denis
>> 
>> Thanks for your time
>> 
>> My external IP address is 88.87.166.18
>> 
>> "are you using browser addons that may send requests to our website”, but 
>> 
>> Not sure about that, but I can say that this problem only started yesterday, and I did not change browser add-ons then. And I get the same 403 error when just trying to pull using “curl” at the command line
>> 
>> Browser add-ons I do use:
>> Firefox:
>>  cliget
>>  DuckDuckGo
>>  Ghostery
>>  HTTPS Everywhere
>>  Imagus
>>  NoScript
>>  Reddit Enhancement Suite
>>  TinEye Reverse Search
>>  uBlock origin
>>  
>> Chrome:
>>  Chrome Remote Desktop
>>  Google Docs
>>  Google Docs offline
>>  Google Sheets
>>  Google Slides
>>  Quick Tab
>>  
>> Safari:
>>  None
>> 
>>> On 28 Mar 2017, at 15:11, Denis Ah-Kang <denis@w3.org> wrote:
>>> 
>>> 
>>> 
>>> On 03/28/2017 05:14 PM, jalanb wrote:
>>>> Hello the list,
>>>> 
>>>> I need help with working around 403 errors from all URLs under https://www.w3.org
>>>> 
>>>> Accessing any URL from Firefox browser (including top-level https://www.w3.org/) gives me 403 errors, and same for other browsers, starting yesterday. I have a few machines at home, all on same WiFi network, and this only happens on one of them. 
>>>> 
>>>> 
>>>> I have seen the page at https://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic/, but that talks of 503 errors, not 403. I assume it is possible that some software on “the bad machine” has been causing excess traffic to you, but I have no idea what software that is, and would be surprised if your response to that also includes accesses to the top-level https://www.w3.org/. Hence I doubt that I’m actually caught by your excess traffic “defences”.
>>>> 
>>>> Any suggestions what else may be going wrong here, any other workarounds?
>>>> 
>>> 
>>> Hi,
>>> 
>>> Can you please provide your IP address? This will help checking which
>>> resources you are requesting.
>>> Also, are you using browser addons that may send requests to our
>>> website?
>>> 
>>> Regards,
>>> 
>>> Denis
>> 
>

Received on Wednesday, 29 March 2017 11:17:10 UTC