Unable to upload using CURL getting 404 Error on Wetransfer.com

SafeSquid Data Loss Prevention module introduced to restrict end users from uploading sensitive or critical information outside the corporate network to prevent data leakage.(Policy Based Upload Control)
India sakshidalvi
Posts: 15
Joined: Thu Jun 03, 2021 9:42 am

Unable to upload using CURL getting 404 Error on Wetransfer.com

Post by sakshidalvi » Wed Jun 16, 2021 10:17 am

I created policy for Checkpoint 5 Upload Control it is working properly in browser but when I tried upload using CURL I was able to upload on file.io
which was bypassed from Upload Block.
file.io uploaded using curl.png
file.io uploaded using curl.png (12.6 KiB) Viewed 3159 times
When I tried Uploading file on https://wetransfer.com via CURL it is redirecting me to the 404 Error page. I was able to access the same URL using Browser.
404 Error Wetransfer.png
404 Error Wetransfer.png (26.68 KiB) Viewed 3159 times
The page that CURL is Fetching - https://wetransfer.com/404

I am unable to find any solution for the same.

India sakshidalvi
Posts: 15
Joined: Thu Jun 03, 2021 9:42 am

Re: Unable to upload using CURL getting 404 Error on Wetransfer.com

Post by sakshidalvi » Wed Jun 16, 2021 11:05 am

I tried troubleshooting again and found out that in cmd if I didn't use the --proxy then I was not able to access. I tried running the same command with --proxy and it was successful.
command new.png
command new.png (4.54 KiB) Viewed 3154 times
After running the above command I got the following output :
output of wetransfer.png
output of wetransfer.png (46.31 KiB) Viewed 3154 times
So now it is blocking upload when I try using curl and if I put wetransfer.com in exception category then I am not getting the error. However, when I upload any file on file.io I get the output with 'success' but if I try the same on we transfer I am getting blank output.
file .io success but we transfer nothing.png
file .io success but we transfer nothing.png (17.47 KiB) Viewed 3154 times

India aashish97
Posts: 117
Joined: Sat Jul 06, 2019 10:45 am

Re: Unable to upload using CURL getting 404 Error on Wetransfer.com

Post by aashish97 » Thu Jun 17, 2021 4:09 am

Hello Sakshi,

The Right way to analyze the Problem is to access the SafeSquid Native Logs.
https://docs.safesquid.com/wiki/Analyze ... Squid_Logs

Gather the details of this Particular Request and check why their was no Response Received
Also use
--verbose
option in curl to see the Headers for better debugging.

Secondly,
The WeTransfer Upload that your are trying via CURL is incorrect. Inorder to Validate First try to Upload to WeTransfer via same Curl without Proxy Option.( i.e. Without Proxy )
If the Upload is Successful, then you are going on the Right Track.
Then via Proxy You are performing the Right Operation.

When Performing Upload to file.io via Curl it works fine with & without Proxy.

India sakshidalvi
Posts: 15
Joined: Thu Jun 03, 2021 9:42 am

Re: Unable to upload using CURL getting 404 Error on Wetransfer.com

Post by sakshidalvi » Thu Jun 17, 2021 11:06 am

Sir I tried uploading file using both -F and -T still I am getting the same 404 error. Even when I upload without any proxy I am getting this error.

I ran the --verbose with the command and here is the output :
verbose ss 1.png
verbose ss 1.png (47.43 KiB) Viewed 3136 times
verbose 2.png
verbose 2.png (53.92 KiB) Viewed 3136 times

I also found that wetransfer have a option to upload via terminal using it wtclient

I found this here - https://stackoverflow.com/a/61336112

I tried uploading using its terminal and the file uploaded successfully.


I am unable to find solution to the 404 error that I am facing in curl.
wetransfer terminal upload.png
wetransfer terminal upload.png (27.61 KiB) Viewed 3136 times

India aashish97
Posts: 117
Joined: Sat Jul 06, 2019 10:45 am

Re: Unable to upload using CURL getting 404 Error on Wetransfer.com

Post by aashish97 » Fri Jun 18, 2021 4:54 am

Hello Sakshi,

The Curl Command is Incorrect and therefore you are getting 404 Error.
This is not How Upload Happens in WeTransfer it can work in others.

Try to use wtclient via Proxy

Post Reply