@Fox The first place I noticed the problem was when I added a visual to the interface. I added a text link to the interface from the 'textlink' section in the open blocks and inserted an image into it. My aim was to have no text inside and only redirect to a link when the image is clicked. However, no matter how much I removed the predefined "New Link" text, whenever I made an addition or deletion to the interface, it would reappear. To solve this issue, I set the font-size of the text link to 0 using CSS, which prevented the "New Link" text from appearing. The problem I'm talking about is probably similar to what I experienced with the text link. The default values assigned by the system, even if you change them, revert back to the values defined by the system when something new is added to the interface or when a setting is changed (for example, background color or deleting a button). Currently, to overcome this issue, I am constantly keeping a backup of the HTML. Whenever I make a new change, I copy the content from the backup, and this is how I'm trying to deal with it, but it's clear there is a problem. Hopefully, it will be resolved soon.
httpclient Bug ?
-
@support just found out that httpclient is not sending custom headers in the order they are set.
Example - Header set in BAS httpclient
After Request sent
( image from fiddler )
As you can see above, the headers are misplaced and are not sent as set in httpclient.
BAS Version - 20.7.6
-
Made some changes, additional headers will preserve its order after 20.8.6 version.
But that doesn't concern standart headers likeAccept,Connection,Host,Cookie
You also setHostandConnectionheader and this may be dangerous, it is better to let http client do it. -
Sorry, but I'll probably won't include this change. Caus there are still many differences,
Accept-Encodingfor example.
Web standarts says, that header order could be arbitrary so it shouldn't be a big problem.
If you want to set headers order in http client, you will probably need to modify libcurl source(
