On Oct 12, 8:59 am, MorningZ wrote:
> "This change failed to remedy the problem"
>
> As it shouldn't...
>
> because the bottom line is: the browser makes the request and the
> browser receives the request, and when the browser sees "text/json"
> come back from the server, it has no idea what to
"This change failed to remedy the problem"
As it shouldn't...
because the bottom line is: the browser makes the request and the
browser receives the request, and when the browser sees "text/json"
come back from the server, it has no idea what to do with it so it
prompts to download the file
On Oct 10, 9:16 am, Jim wrote:
> On Oct 9, 8:50 pm, MorningZ wrote:
>
> > it's supposed to be "application/json", not "text/json". set the
> > content type properly in your server side code and you'll be fine...
> > "text/plain" will work as well
>
> After some further searching, I found t
On Oct 9, 8:50 pm, MorningZ wrote:
> it's supposed to be "application/json", not "text/json". set the
> content type properly in your server side code and you'll be fine...
> "text/plain" will work as well
After some further searching, I found this section of code in the
jQuery library. If
On Oct 9, 8:50 pm, MorningZ wrote:
> it's supposed to be "application/json", not "text/json". set the
> content type properly in your server side code and you'll be fine...
> "text/plain" will work as well
>
I don't have control over the server code - is there any other
possible work aroun
it's supposed to be "application/json", not "text/json". set the
content type properly in your server side code and you'll be fine...
"text/plain" will work as well
On Oct 9, 8:12 pm, Jim wrote:
> I have a file upload form (see end of email) that I am am processing
> with jQuery so that it c
6 matches
Mail list logo
