Page MenuHomePhabricator

domain added to $wgCopyUploadsDomains in production?
Closed, InvalidPublic

Description

Hi,

I have a problem uploading files from our server tot wikimedia.org.
There is no problem in the beta environment.
I didn't make a request to add our domain (*.ic.uva.nl) in the whitelist on wikimedia.org, but the domain is in the drop down list on the GWtoolset page.
Therefore I thought a separate request wasn't needed. But maybe I'm wrong?
There are no restrictions for access on our server (Example image at http://angel.ic.uva.nl:8504/UBA01_IZ19800123.tif)

Best wishes,

Erik
University of Amsterdam

Event Timeline

Reedy renamed this task from domain addded to $wgCopyUploadsDomains in production? to domain added to $wgCopyUploadsDomains in production?.Dec 12 2016, 2:50 PM

'The domain whitelist was requested at T150167. Apparently, yes, you did.

I can't test your example file, as you offered http://angel.ic.uva.nl:8504/UBA01_IZ16100277.tif but this is now a 403.

I'm sorry. In the process of setting up a batch to process, I deleted the test images. I restored the image in the examples above.

The error message I get is:
The media file URL could not be evaluated. The URL delivers the content in a way that is not yet handled by this extension or there was an HTTP request issue. URL given was "http://angel.ic.uva.nl:8504/UBA01_IZ19800123.tif". HTTP request error "There was a problem during the HTTP request: 403 Forbidden".

'The domain whitelist was requested at T150167. Apparently, yes, you did.

I can't test your example file, as you offered http://angel.ic.uva.nl:8504/UBA01_IZ16100277.tif but this is now a 403.

My browser can download this image. Is it still 403?

And yes,https://noc.wikimedia.org/conf/highlight.php?file=InitialiseSettings.php says (by *.ic.uva.nl', // University of Amsterdam - T150167) that the domain is whitelisted.

Yes, it is still a 403. I can download the image from the browser, but the error message appears when uploading in the GW toolset.

Could be a protection allowing some but not all user agents, to avoid automatic crawlers for example.

Please get in touch with the persons with the responsibility to administrate the http://angel.ic.uva.nl:8504 web server and ask them to check error logs around 2016-12-13 11:40 UTC to check what triggers this 403.

The upload actions were not traceable in the server logs.
We tried the upload on another server in the same domain and that works perfect.
So it must be something on our side, although it is mysterious what it could be.

Urbanecm changed the task status from Resolved to Invalid.Dec 16 2016, 1:01 PM

Invalid from my POV as there was nothing we can resolve.