Accept request header always set to 'text/*' when reverting to FileApi

[mbyrne00]

When using the plugin with a HTML5 compatible browser it produces a request with the Accept request header as 'application/json', however the FileApi (flash) code always produces an Accept header of 'text/*'.

I can't find a way to override this and this causes issues with Java server-side code.

Any workarounds in the mean time would be greatly appreciated.

The following have been tried and have no effect:

1. Setting headers in $upload:
   $upload.upload({headers: {accept:'application/json',....}})

2. Editing angular-file-upload-shim.js and forcing header config
   // Hack to try to force headers to be passed to FileAPI
   config.headers = {'Accept': 'application/json'};
   // Existing line below
   xhr.__fileApiXHR = FileAPI.upload(config);

After making each of the above changes and sniffing the traffic, the Accept header was still 'text/*'

[danialfarid]

Add below lines here https://github.com/danialfarid/angular-file-upload/blob/master/dist/angular-file-upload-shim.js#L113

FileAPI.accept = 'application/json';
config.accept = 'application/json';

If that works I do a fix release tomorrow.

[mbyrne00]

Hey Danial - thanks a lot for the quick response but all my code is at work and I'm home for the weekend now so won't be able to try again until Monday (Australian timezone).

I will definitely give it a go and feedback although I did a bit of searching on the train ride home and after looking at the flash API http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/net/FileReference.html#upload() and other comments on FileAPI https://github.com/mailru/FileAPI/issues/59 I don't hold out much hope. I think the Flash API itself is too inflexible to allow it.

I'll let you know how I get on after the weekend.

[danialfarid]

Yea you are right it doesn't work.
We gotta wait for FileAPI new release to see if it fixes it or not. https://github.com/mailru/FileAPI/issues/189#issuecomment-33807468

[mbyrne00]

Hmm ok - looks like you have proven it won't work :-(

I'll look at fudging the backend to allow 'text/*' for JSON.

Thanks for checking this out though!

[danialfarid]

No easy solution or alternative for this and there are server workarounds for this issue.