Server header should provide MAAS version

Bug #1722538 reported by Mike Pontillo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Low
Unassigned

Bug Description

When I hit the MAAS server via HTTP and examine the headers, the `Server` header isn't very useful:

$ curl -I http://192.168.100.2:5240/MAAS/metadata/
HTTP/1.1 401 UNAUTHORIZED
Server: TwistedWeb/16.0.0
Vary: Authorization, Cookie
X-Frame-Options: SAMEORIGIN
Content-Type: text/plain
X-Maas-Api-Hash: 078f0ca2111f97fabd2994766c54e616479bcc07
Date: Tue, 10 Oct 2017 14:01:16 GMT

It would be nice if it reported the MAAS version, such as:

Server: MAAS/2.3.0~beta1

Tags: papercut
tags: added: papercut
Changed in maas:
milestone: none → 2.3.0
Changed in maas:
milestone: 2.3.0 → 2.3.x
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
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.