I've got a servlet which returns a binary stream (a jpeg, for example). The browser on the 3650 displays it fine when used over a normal HTTP connection. But when it is done via SSL, it tries to save it as "https://XXX.XXX.XXX.XXX" instead of displaying it, and if I try to save it, the browser crashes and the message "App closed Browser KERN-EXEC 0" is displayed. Same result in 7650. It seems to work fine on the 7250 via SSL.
If it is done via a non-SSL connection, and the HTTP header "Content-disposition" is set to "attachment;filename=xxxxxx", the display is fine, but it is not saved with the given file name. Instead the last item in the URI (not parameters) is used just as though the Content-disposition header is not set, eg. "download" is used when the URI is "http://18.104.22.168/abc/dowload?abc=def&fgh=jik"
Are my suspicions correct?