When crashsender receives a 301 or 302 redirect response, it will have to
upload the entire crash dump a second time. It would be nice if there was an
initial GET request to say hello and get any redirect information before the
POST request happens.
What steps will reproduce the problem?
1. Configure server A to redirect crash submissions to server B.
2. Submit a crash report to server A. The entire report is uploaded, then
server A responds with "302 moved temporarily" and crashsender has to start all
over again with server B. Crash reports can be very large and this duplicate
submission seems wasteful.
What is the expected output? What do you see instead?
Crashsender should submit a GET request to server and if it doesn't get back a
200 response, it should take appropriate action - report the error or process
the redirect and start over.
What version of CrashRpt are you using?
What is your version of Visual Studio?
What is your version of Windows operating system?
Please provide any additional information below.
Original issue reported on code.google.com by c...@c-riddell.com on 26 Aug 2014 at 7:25
Original issue reported on code.google.com by
c...@c-riddell.comon 26 Aug 2014 at 7:25