Skip to main content
15 events
when toggle format what by license comment
Feb 27 at 10:43 comment added jdweng The default browser on the server or the User-Agent defined in the HTML webpage.
Feb 27 at 10:02 comment added ch4 @jdweng Thank you for the links. So I've looked at the headers from the console client and the user-agent is empty (server shows null). What would it default to on the server in that case? I'm going to try make the headers in the console client the same as the headers that would be sent from the website and see if that helps them
Feb 26 at 18:36 comment added jdweng User-Agent is an HTTP Header. The list of different settings for User-Agent are shown here : developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent Also see support.west-wind.com/Thread5KX0SY4SX.wwt
Feb 26 at 15:43 comment added ch4 @jdweng I've tried uploading the file via postman and worked fine on mine so will try replicate the steps with the customer. But I am confused about the browser/useragent. On postman the user-agent is 'PostmanRuntime/...' but how/what do I change this too? Would love a little guidance on what you mean and how to check which browser the server would be defaulting to?
Feb 21 at 13:32 comment added jdweng The bad server could be defaulting to a different browser. Also in postman check the UserAgent which is the browser that is used by the server.
Feb 21 at 9:29 comment added ch4 @JalpaPanchal Have tried with smaller files too and same error. The issue is I cant replicate the issue on any of our builds. It only happens on a customers server so hard to debug and test stuff. We'll see if we can get them to try postman and see if it works from there.
Feb 21 at 9:25 comment added ch4 @jdweng Thats a good shout. Will have a look at that today. But that wouldnt explain why the command line client works fine on other servers but fails on this one no?
Feb 21 at 9:25 comment added Jalpa Panchal you could try other client like postman or something else to test the result s that we can chek if the issue is with the command line client or in the iis configuration. and use the fiddler tool to capture both the request and compare that request and see what is missing in the console client. Have you tried uploading the small file using command line client what was the result?
Feb 20 at 22:21 comment added jdweng It could be the content length in the http header. Try uploading with Postman and then check in the control panel Raw Http. Compare the content length in Postman against what you are using in c#.
Feb 20 at 21:15 comment added ch4 @jdweng I think I understand that but that wouldnt explain why the same file uploads fine when I upload it via the website. The error only occurs when using a console command line client to upload the file to the same server endpoint the website uses
Feb 20 at 19:14 history edited marc_s CC BY-SA 4.0
added 71 characters in body; edited title
Feb 20 at 17:00 comment added jdweng I suspect this has to do with file extensions and applications that are used with the extensions. Each section of the multipart contains a file type (see learn.microsoft.com/en-us/previous-versions/office/developer/…. The problem may be an application is not installed in the server.
Feb 20 at 16:50 review Close votes
Feb 24 at 0:05
S Feb 20 at 16:23 history asked ch4 CC BY-SA 4.0
S Feb 20 at 16:23 history created from staging ground Graduated from staging ground post.