[2.1.5] apt http(s) proxy invalid url for custom TLD

Bug #1679689 reported by Felipe Reyes
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Unassigned

Bug Description

[Impact]

MAAS UI doesn't allow the use of custom TLD when setting the "APT & HTTP/HTTPS proxy server"

[Test Case]

* Go to Settings > Network Configuration
* Set the APT proxy to http://example.travel:3128/
* Save the configuration

Expected result:

* The apt proxy is set to http://example.travel:3128/

Actual result:

the save operation fails with the error "Enter a valid URL"

[Other Info]

The TLD '.maas' was whitelisted and it works. In my lab I have multiple vlans and each vlan holds a TLD (e.g.: some-host.vlan10) so I can only access my local proxy through the IP.

Tags: proxy
Revision history for this message
Gavin Panella (allenap) wrote :

On the face of it MAAS really shouldn't have any business limiting which domains are in use.

Changed in maas:
status: New → Triaged
importance: Undecided → Critical
tags: added: proxy
Changed in maas:
milestone: none → 2.2.0
Changed in maas:
milestone: 2.2.0 → 2.2.x
Changed in maas:
milestone: 2.2.x → 2.3.0
Revision history for this message
Andres Rodriguez (andreserl) wrote :

I believe this issue is now resolved in MAAS 2.2+. (I've tested both 2.2.1 and 2.3.0 and have been unable to reproduce).

Changed in maas:
milestone: 2.3.0 → none
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.