Originally created by @FabianBartl on GitHub (Sep 1, 2025).
I updated to Pangolin v1.9.3 today, and wanted to change an IP/Hostname field of a Resource, but after saving the changes I got a Bad Request error.
The Issue is, that the Method and Port fields are reset to their default just by clicking in the IP/Hostname field and then somewhere else outside it, like saving the changes.
Originally created by @FabianBartl on GitHub (Sep 1, 2025).
I updated to Pangolin v1.9.3 today, and wanted to change an IP/Hostname field of a Resource, but after saving the changes I got a Bad Request error.
The Issue is, that the Method and Port fields are reset to their default just by clicking in the IP/Hostname field and then somewhere else outside it, like saving the changes.
@Pallavikumarimdb commented on GitHub (Sep 1, 2025):
After recent change where the system auto-parses full URLs from the IP/Hostname field. It looks like the parse host target logic is being triggered even when values for method/port are already present, which causes them to reset to defaults unexpectedly.
I’m looking into this and will fix soon so that existing values for Method and Port are preserved unless the user explicitly changes them.
@Pallavikumarimdb commented on GitHub (Sep 1, 2025):
After recent change where the system auto-parses full URLs from the IP/Hostname field. It looks like the parse host target logic is being triggered even when values for method/port are already present, which causes them to reset to defaults unexpectedly.
I’m looking into this and will fix soon so that existing values for Method and Port are preserved unless the user explicitly changes them.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @FabianBartl on GitHub (Sep 1, 2025).
I updated to Pangolin v1.9.3 today, and wanted to change an IP/Hostname field of a Resource, but after saving the changes I got a Bad Request error.
The Issue is, that the Method and Port fields are reset to their default just by clicking in the IP/Hostname field and then somewhere else outside it, like saving the changes.
@Pallavikumarimdb commented on GitHub (Sep 1, 2025):
After recent change where the system auto-parses full URLs from the IP/Hostname field. It looks like the parse host target logic is being triggered even when values for method/port are already present, which causes them to reset to defaults unexpectedly.
I’m looking into this and will fix soon so that existing values for Method and Port are preserved unless the user explicitly changes them.