Page 1 of 1

403 forbidden on one IP but not in other

Posted: Tue Aug 15, 2017 7:08 am
by excellenting
Hi.

I get on production server a 403 in curl error, when try download with post method. (Application work fine usually on producction for last 4 weeks)

Code: Select all

The requested URL returned error: 403 Forbidden
Debug

Code: Select all

curl resource {@399
  url: "https://ops.epo.org/3.2/rest-services/published-data/publication/epodoc/biblio"
  content_type: null
  http_code: 403
  header_size: 0
  request_size: 1175
  filetime: -1
  ssl_verify_result: 0
  redirect_count: 0
  total_time: 0.275351
  namelookup_time: 0.253966
  connect_time: 0.254693
  pretransfer_time: 0.265886
  size_upload: 873.0
  size_download: 0.0
  speed_download: 0.0
  speed_upload: 3170.0
  download_content_length: -1.0
  upload_content_length: 873.0
  starttransfer_time: 0.275341
  redirect_time: 0.0
  redirect_url: ""
  primary_ip: "52.48.115.XX"
  certinfo: []
  primary_port: 443
  local_ip: "172.31.46.XXX"
  local_port: 47840
}
Body of POST

Code: Select all

CN201359673Y,CN2840265Y,CN2390221Y,CN2524434Y,CN2446062Y,CN201928301U,KR100736254B1,CN2243591Y,CN201281060Y,CN201540252U,CN202911969U,CN203021052U,CN203382252U,CN203497701U,CN203865541U,CN100469135C,DE20215605U1,CN202587260U,CN202508946U,CN202030322U,CN201721599U,CN2869125Y,CN202549923U,CN201663177U,CN2821806Y,CN201096939Y,CN203631158U,JP4019159B,CN2900428Y,DE202004003040U1,CN2685292Y,CN200964297Y,CN2356972Y,CN202007582U,CN2287660Y,CN200999499Y,CN2888019Y,KR100801089B1,DE20200672U1,CN202284163U,CN200990259Y,CN202871352U,CN204066796U,JPS4417711Y1,CN2405618Y,KR101181032B1,CN201367756Y,CN201610637U,KR100704963B1,TW348740B,JP3150048U,JP4951970B2,CN202412285U,CN205238039U,CN205928497U,CN2452239Y,CN202277319U,CN205422276U,DE202011101269U1,CN202591611U,USD213210S,USD248881S,USD553351S,USD578534S,USD627963S,CN201198220Y,CN2765771Y,CN201729528U,CN202855550U,CN203747750U
If try download this biblio form develop office or on EPO Portal with credentials, not problem.
Only get forbidden on production IP.

Apreciate help

Re: 403 forbidden on one IP but not in other

Posted: Wed Aug 16, 2017 10:09 am
by EPO / OPS Support
Dear user,

We had to take measures due to misuse of the services and filter out some ranges of IP.
The two IPs I see in your screenshot were not affected. Maybe you used another IP.
Please contact us at patentdata@epo.org.

You should only use "EPO portal with credentials" for production.
The other area is only for testing and is very restricted.

Kind regards,
OPS support

Re: 403 forbidden on one IP but not in other

Posted: Wed Aug 16, 2017 3:15 pm
by excellenting
Hi
I don't know why curl retunr this ips.

Any ip is own IP.

Code: Select all

curl ipinfo.io/ip
52.211.240.1XX
I think that curl response not return REAL IP. Return a FORWARDER IP.

Local ip is a 172.31.46.XXX not public IP.

Re: 403 forbidden on one IP but not in other

Posted: Fri Aug 18, 2017 10:52 am
by excellenting
Problem persist

Try on VPS on OVH and same problem.

Send email to patentdata@epo.org two days ago and any response.

Apreciate help and support.

We try on several locations, and same result.

Only work fine on Develop IP on Spain.

Code: Select all

curl resource {@403
  url: "https://ops.epo.org/3.2/rest-services/published-data/publication/epodoc/biblio"
  content_type: null
  http_code: 403
  header_size: 0
  request_size: 1175
  filetime: -1
  ssl_verify_result: 0
  redirect_count: 0
  total_time: 0.089939
  namelookup_time: 0.004215
  connect_time: 0.019582
  pretransfer_time: 0.059218
  size_upload: 873.0
  size_download: 0.0
  speed_download: 0.0
  speed_upload: 9706.0
  download_content_length: -1.0
  upload_content_length: 873.0
  starttransfer_time: 0.089925
  redirect_time: 0.0
  redirect_url: ""
  primary_ip: "52.211.151.90"
  certinfo: []
  primary_port: 443
  local_ip: "5.135.93.73"
  local_port: 39362
}

Re: 403 forbidden on one IP but not in other

Posted: Fri Aug 18, 2017 12:19 pm
by EPO / OPS Support
Hi,

Sorry for late reply, but there were holidays in Austria this week.

We have issues in POST which will only be fixed with the next maintenance release planed in September. Please use POST in 3.1 in the meantime.

We are sorry not to be of help at this point, but version 3.1 should work properly.

Regards,
OPS support