Jump to content
Updated Privacy Statement
  • 5

Sharefile file upload api not working for multiple files - Bad Request -100 - Business Critical


Vijayaragavan Seshadri

Question

Recommended Posts

  • 0
14 hours ago, Kevin Glenn said:

@Daniel Williams - Thank you for providing the additional information. Unfortunately we are going to need a Fiddler trace that captures the network traffic (with HTTPS decrypted) so we can identify a root cause. Otherwise we won't be able to identify a solution. As soon as we have that collected and verified we can opt your account out of the update and get you back in working order.

 

@Senthilkumar Natarajan - Thank you for providing the network capture. We have opted your account out of the update until we can identify the root cause and implement a fix. You should no longer be seeing the apiadapter request URLs for the time being. Future updates will be handled through your support case, SR#81102583.

Hi Kevin, Our sysadmins have tools for monitoring network traffic. It may not be the Fiddler tool but I'm sure they can trace whatever you need to see. Can we set up a phone conference so we can talk specifics?

Link to comment
  • 0

Hi Daniel,

 

Unfortunately toggling accounts in and out of this specific update is not something that can be easily done. And unless we have a network capture with HTTPS traffic decrypted to identify and address the root cause then as soon as we make the changes permanent we'll be right back in the same situation. We're already looking to move forward with this as a permanent change but haven't done so yet specifically so that once we receive your network capture we can opt your account out until we identify and implement a fix. We won't be able to stay in this mixed state for very long so please make sure to get us the requested information as soon as possible so we can start working on a solution. Thank you for your understanding and we look forward to investigating your situation as soon we have that network capture.

Link to comment
  • 0
16 hours ago, Kevin Glenn said:

Hi Daniel,

 

Unfortunately toggling accounts in and out of this specific update is not something that can be easily done. And unless we have a network capture with HTTPS traffic decrypted to identify and address the root cause then as soon as we make the changes permanent we'll be right back in the same situation. We're already looking to move forward with this as a permanent change but haven't done so yet specifically so that once we receive your network capture we can opt your account out until we identify and implement a fix. We won't be able to stay in this mixed state for very long so please make sure to get us the requested information as soon as possible so we can start working on a solution. Thank you for your understanding and we look forward to investigating your situation as soon we have that network capture.

Kevin, My request to have Fiddler installed on a test server is meeting with concerns by our Cyber Security group. (As expected.) I'm going to try to find another web API debugging tool or package that I can incorporate into our development code to meet your demands.

Link to comment
  • 0
On 4/5/2022 at 3:37 PM, Tanner Smith1709163332 said:

I am receiving a similar response, Kevin. Would love to find a fix for this so I can finish this integration. 

 

Hi Tanner,

 

We typically wouldn't assist with new implementations, however, due to the recent changes we've made with the API endpoints for uploading I definitely want us to take a look at any reports of uploads failing. Please open a support case and provide a Fiddler trace with HTTPS traffic decrypted so we can further investigate. Feel free to post your support case here and I'll work with our Support team to help investigate. Instructions to capture a Fiddler trace are posted earlier in this thread. 

Link to comment
  • 0
21 hours ago, Kevin Glenn said:

 

Hi Tanner,

 

We typically wouldn't assist with new implementations, however, due to the recent changes we've made with the API endpoints for uploading I definitely want us to take a look at any reports of uploads failing. Please open a support case and provide a Fiddler trace with HTTPS traffic decrypted so we can further investigate. Feel free to post your support case here and I'll work with our Support team to help investigate. Instructions to capture a Fiddler trace are posted earlier in this thread. 

Thanks, Kevin. We actually got it figured out. Thank you for the assistance though. 

Link to comment
  • 0
On 4/13/2022 at 8:15 AM, Daniel Williams1709163319 said:

Hello Kevin, I've uploaded the trace you requested attaching it to Case #81106877. Please look at it at your earliest convenience. We have been receiving upload failures through the API since 23MAR2022. We're uploading hundreds of files a day manually since then. We really need you to look at this soon.

 

Hi Daniel,

 

Thank you very much for providing that. I just spoke with Citrix Engineering and they were able to identify the cause. The short of it was there was a minor defect with our older file transfer infrastructure that ignored content length (file size) mismatches and allowed uploads to go through when they should have actually failed. This is something we correctly block in the our infrastructure and will be keeping it as is. More detailed information should be coming to you through your support case. We suggest taking action on this feedback and updating your scripts accordingly. From what I saw in the feedback, there may be multiple options to address the cause based on your specific needs, however, it sounds like you'll simply want to set "raw=false" in your upload requests. 

Link to comment
  • 0
On 4/12/2022 at 8:23 PM, Paul Naylor said:

We are also experiencing this same issue. API has been working for over a year until around 3-22-2022.

 

We have opened a case: 81105553

New ShareFile Errors Sent To SLM 4-12-2022.txt 6.1 kB · 0 downloads

 

Hi Paul,

 

We are going to need a network capture with HTTPS traffic decrypted. Fiddler is a great option for this but there are certainly other proxy tools that can output this information as well. 

Link to comment
  • 0

Hi @Kevin Glenn , we are experiencing the same issue when attempting to upload files. Our API integration hasn't changed in years but since march/april we are receiving "ERROR: REJECTED" response with a HTTP 200 status code. I have tried adding the raw=false param that seems to have worked for others here but that made no difference for us.
We are doing a form POST as described in the docs: https://api.sharefile.com/samples/ruby

def multipart_form_post url, file_path 
  newline = "\r\n"
  filename = File.basename(file_path)
  boundary = "----------#{Time.now.nsec}"
     
  uri = URI.parse(url)
   
  post_body = []
  post_body << "--#{boundary}#{newline}"
  post_body << "Content-Disposition: form-data; name=\"File1\"; filename=\"#{filename}\"#{newline}"
  post_body << "Content-Type: application/octet-stream#{newline}"
  post_body << "#{newline}"
  post_body << File.read(file_path)
  post_body << "#{newline}--#{boundary}--#{newline}"
   
  request = Net::HTTP::Post.new(uri.request_uri)
  request.body = post_body.join
  request["Content-Type"] = "multipart/form-data, boundary=#{boundary}"
  request['Content-Length'] = request.body().length
 
  http = Net::HTTP.new uri.host, uri.port
  http.use_ssl = true
  http.verify_mode = OpenSSL::SSL::VERIFY_NONE
   
  response = http.request request
  return response
end

Can you (or someone) please assist us with this issue? Thanks!

Link to comment
  • 0
11 hours ago, Ashton CL said:

Hi @Kevin Glenn , we are experiencing the same issue when attempting to upload files. Our API integration hasn't changed in years but since march/april we are receiving "ERROR: REJECTED" response with a HTTP 200 status code. I have tried adding the raw=false param that seems to have worked for others here but that made no difference for us.
We are doing a form POST as described in the docs: https://api.sharefile.com/samples/ruby

def multipart_form_post url, file_path 
  newline = "\r\n"
  filename = File.basename(file_path)
  boundary = "----------#{Time.now.nsec}"
     
  uri = URI.parse(url)
   
  post_body = []
  post_body << "--#{boundary}#{newline}"
  post_body << "Content-Disposition: form-data; name=\"File1\"; filename=\"#{filename}\"#{newline}"
  post_body << "Content-Type: application/octet-stream#{newline}"
  post_body << "#{newline}"
  post_body << File.read(file_path)
  post_body << "#{newline}--#{boundary}--#{newline}"
   
  request = Net::HTTP::Post.new(uri.request_uri)
  request.body = post_body.join
  request["Content-Type"] = "multipart/form-data, boundary=#{boundary}"
  request['Content-Length'] = request.body().length
 
  http = Net::HTTP.new uri.host, uri.port
  http.use_ssl = true
  http.verify_mode = OpenSSL::SSL::VERIFY_NONE
   
  response = http.request request
  return response
end

Can you (or someone) please assist us with this issue? Thanks!

 

Hi Ashton,

 

If you could please get a support case opened that would be greatly appreciated. You can include exactly what you mentioned in your comment here and then if you can also collect a network capture that decrypts HTTPS traffic we can have our engineering team take a look. Just let your support representative know to reach out to me directly and/or you can post your case number here. 

Link to comment
  • 0
On 7/1/2022 at 10:13 PM, Kevin Glenn said:

 

Hi Ashton,

 

If you could please get a support case opened that would be greatly appreciated. You can include exactly what you mentioned in your comment here and then if you can also collect a network capture that decrypts HTTPS traffic we can have our engineering team take a look. Just let your support representative know to reach out to me directly and/or you can post your case number here. 


Thanks @Kevin Glenn!
I have created a support case, 81283253 and sent along the request body for the engineers to inspect.
Please let me know if there's anything further you need from my end.
 

Link to comment
  • 0
On 7/4/2022 at 5:30 AM, Ashton CL said:


Thanks @Kevin Glenn!
I have created a support case, 81283253 and sent along the request body for the engineers to inspect.
Please let me know if there's anything further you need from my end.
 

 

Thanks Ashton! I've raised a case with Citrix Engineering and linked it to your support case. Just be aware that we may require a network trace to see the full unencrypted traffic. We'll keep you posted though. 

Link to comment
  • 0

Hi Ashton,

 

Taking a look at our backend logging we're seeing an exception of "Create was missing either parentID, fileName, or filePath (SINGLE CREATE)" and then if we look at the UploadInfo in the same log entry we see an empty value for filename. Which is interesting because the details you manually provided do appear to have a value for that.

<Item key="filename" value="" />

We attempted to reproduce the behavior on our end using the exact details you provided, but our tests were all successful.  To further investigate, we will require a network capture showing the full request and response with HTTPS decrypted. There are a few comments in this thread outlining the process. Here's a couple examples:

 

https://discussions.citrix.com/topic/415895-sharefile-file-upload-api-not-working-for-multiple-files-bad-request-100-business-critical/page/4/#comment-2090070

 

https://discussions.citrix.com/topic/415895-sharefile-file-upload-api-not-working-for-multiple-files-bad-request-100-business-critical/#comment-2089525

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...