HTTP Sender displays random charset encoding when clicking between channel destinations

rbeckman-nextgen / test-mc3

0 stars 0 forks source link

HTTP Sender displays random charset encoding when clicking between channel destinations #4219

Closed rbeckman-nextgen closed 4 years ago

rbeckman-nextgen commented 4 years ago

Steps to reproduce -Create channel -Create two destinations, assign both HTTP Sender -Click between the two destinations

Expected Behavior: Charset Encoding will not change Actual Behavior: Charset encoding will display a seemingly random value from the available options each time you select destination 1.

Imported Issue. Original Details: Jira Issue Key: MIRTH-4363 Reporter: mpang Created: 2019-01-09T16:00:25.000-0800

rbeckman-nextgen commented 4 years ago

If you set destination 2 to a connector type other than HTTP sender first, then change it to HTTP sender, then a random will be displayed each time either destination (both are now HTTP Sender) is clicked

Imported Comment. Original Details: Author: mpang Created: 2019-01-09T16:03:36.000-0800

rbeckman-nextgen commented 4 years ago

mirthdb=> select * from channel where id = <channelIdHere>; to see that the stored charset value is not changed when clicking through the administrator, just the value in the Administrator.

Imported Comment. Original Details: Author: mpang Created: 2019-01-09T16:06:34.000-0800

rbeckman-nextgen commented 4 years ago

Video attached, try VLC if filetype not supported by video player

Imported Comment. Original Details: Author: mpang Created: 2019-01-09T16:09:26.000-0800

rbeckman-nextgen commented 4 years ago

Exporting and then importing an HTTP Sender channel into MC 3.7.0 encounters the same issue.

A channel that has one or more HTTP sender destinations will be assigned a random encoding (not the one in the channel export) when it is saved.

Imported Comment. Original Details: Author: mpang Created: 2019-01-09T16:30:41.000-0800

rbeckman-nextgen commented 4 years ago

I'm having the same issue on various systems:

Win2008R2 with PostgreSQL 9.6 (java8)
Debian9 with PostgresSQL 10 (java11)

Very annoying bug when having several HTTP senders, modifying something in a transformer step would result in choosing the correct Encoding each time before deployment.

Imported Comment. Original Details: Author: discofris Created: 2019-01-28T04:36:29.000-0800

rbeckman-nextgen commented 4 years ago

If you set Charset Encoding to Default, it never changes. Painful to revisit each channel to do this, but this is a workaround for now if you can stick to the default.

Imported Comment. Original Details: Author: ashishshetty1992 Created: 2019-02-20T06:52:42.000-0800