Digitale Infrastruktur

Steps¶

What steps did you followed?

1. Visit some domain of Piraten Basel via https:// instead of http:// in a browser i.e.
   1. https://piraten-basel.ch/
   2. https://bs.piratenpartei.ch/
   3. https://bl.piratenpartei.ch/

Observation¶

What has happened?

• The server replies with web content obviously hosted for the section of Aargau ( https://www.piraten-aargau.ch/ ) in cutted design.
• I found no possibility to access any data on our section host via https:// instead up to now.

Expectation¶

What have you expected to happen?

• EITHER that the server replies with data from our host
• OR that the server denies any SSL request, replying with an error note.

Plea for immediate fix¶

I set the task priority to immediate.

Possible negative impact risks:

1. Likely very odd impression on visitors, especially non-pirate first-time visitors.
   1. May lead to decreased amount of confidence into our section, i.e.
      1. possible decrease in potential votes
      2. possible decrease in potential support of sympathizers (i.e. donations or actions)
         These risks currently increased as our section participates right now in elections; the most important one for us yet, but likely also important for the whole party.

Unlikely to be mentionned in mass media ever (worste-case impact). But better be safe than sorry.

Request¶

Prefered solution: Fix server config so that SSL requests by HTTPS on our section domains results in content served from our section host.

Alternate solution if way faster to apply: Fix server config so that SSL requests by HTTPS on our section domains results in error messages.

Please use an appropriate category below to be sure the ticket will be assigned to the right person.

Don't forget to ad a Screenshot!