1

This looks simple but I don't know how to fix.

Open the following URL in your browser:

https://ecomm.sella.it/gestpay/gestpayws/WSCryptDecrypt.asmx?WSDL

This seems working and this will download and XML WSDL in your browser.

But on our linux server when I try to wget the same URL it return with 404-Not found error:

wget https://ecomm.sella.it/gestpay/gestpayws/WSCryptDecrypt.asmx?WSDL

At the same time when I try to wget google or hotmail it just works fine. But this WSDL URL returns with 404 error code. Looks like this is some kind of caching issue.

How can I fix this?

Malik Ahmed Khan Awan
  • 113
  • 1
  • 4
  • I get a 404 on both browser and wget. I think your browser has cached instead? – Samar Jun 10 '15 at 21:59
  • I cleared my browser's cache so many times. tried with different browsers and requested my friends on different locations to test this. and the same URL was working everywhere without any 404 error. After your comment I tried to test this on an online proxy and it is working there as well. – Malik Ahmed Khan Awan Jun 10 '15 at 22:04
  • Is it possible that for large website's some URL is working in an area/region like UK but not in another region like ASIA something like propagation issue? But this was working an hour ago on same machine. – Malik Ahmed Khan Awan Jun 10 '15 at 22:05
  • @MalikAhmedKhanAwan this is totally locally based. It opens for Netherlands and Germany's proxy but gives 404 for USA's proxy (apart from my own location) – Samar Jun 10 '15 at 22:13
  • @Samar you are right. This is locally based. I checked this URL now on https://www.uptrends.com/tools/uptime . and it says that this API is not available at the moment in different regions including Rome. Please Answer to this question and then I'll mark it as the Right Answer. :) – Malik Ahmed Khan Awan Jun 10 '15 at 22:30
  • @MalikAhmedKhanAwan yes, correct :) – Samar Jun 10 '15 at 22:35

2 Answers2

1

This is totally locally based. It opens for Netherlands and Germany's proxy but gives 404 for USA's proxy (apart from my own location).

Samar
  • 1,036
  • 8
  • 6
-1

404 is a client side err, if you don't have any typo before query(?) then it would simply mean the server you connected may not have the file you are trying to download. There may be regional servers, the ones missing a deploy, try wget from the same regional host if you have where it worked from browser.

chetangb
  • 145
  • 6
  • Thank you for your answer but this is not client side err. 404 is always server side error. If the server doesn't find a document it returns the 404 status code. And finally we figured out that this is not server or caching issue. the API itself is not accessible in some regions across the world. – Malik Ahmed Khan Awan Jun 10 '15 at 22:34