1993–94 French Division 2

The Division 2 season 1993/1994, organised by the LFP was won by OGC Nice and saw the promotions of OGC Nice, Stade Rennais FC and SC Bastia, whereas FC Rouen, US Valenciennes, FC Bourges and FC Istres were relegated to Division 3.

French Division 2
Season1993–94
ChampionsNice (4th title)
PromotedNice
Rennes
Bastia
RelegatedRouen
Valenciennes
Bourges
Istres
Matches played462
Top goalscorerYannick Le Saux
(27 goals)

22 participating teams

Final table

Pos Team Pld W D L GF GA GD Pts Promotion or Relegation
1 OGC Nice (C, P) 42 18 18 6 47 25 +22 54 Promotion to French Division 1
2 Stade Rennais FC (P) 42 20 13 9 57 38 +19 53
3 SC Bastia (P) 42 21 11 10 44 29 +15 53
4 Nîmes Olympique 42 21 9 12 59 38 +21 51
5 Red Star 42 20 9 13 61 45 +16 49
6 Stade Briochin 42 18 11 13 53 52 +1 47
7 Stade Lavallois 42 16 14 12 56 47 +9 46
8 USL Dunkerque 42 13 16 13 44 51 7 42
9 FCO Charleville 42 14 14 14 41 48 7 42
10 Olympique Alès 42 13 15 14 47 50 3 41
11 CS Sedan Ardennes 42 14 12 16 44 42 +2 40
12 AS Nancy 42 15 10 17 49 48 +1 40
13 FC Gueugnon 42 11 18 13 42 43 1 40
14 FC Mulhouse 43 13 15 15 49 52 3 41
15 ASOA Valence 42 14 11 17 47 47 0 39
16 AS Beauvais 42 10 19 13 45 51 6 39
17 Le Mans UC72 42 14 11 17 43 50 7 39
18 Chamois Niortais FC 42 13 13 16 34 41 7 39
19 FC Rouen (R) 42 15 7 20 45 53 8 37 Relegation to Championnat National
20 US Valenciennes (R) 42 12 13 17 45 59 14 37
21 FC Bourges (R) 42 9 12 21 43 60 17 30
22 FC Istres (R) 42 7 12 23 35 62 27 26
Source:
(C) Champion; (P) Promoted; (R) Relegated.

Recap

Top goalscorers

#PlayerClubGoals
1 Yannick Le Saux Saint-Brieuc 27
gollark: I would probably use nginx, because I'm used to it and it has nicer configuration:```nginxhttp { # whatever important configuration you have for all HTTP servers, `nginx.conf` probably ships with some # fallback in case someone visits with an unrecognized Host header server { listen 80 default_server; listen [::]:80 default_server; return 301 http://somedomain$request_uri; } server { listen 80; # you may (probably do) want HTTPS instead, in which case this bit is somewhat different - you need to deal with certs and stuff, and use port 443 - also you should probably add HTTP/2 listen [::]:80; # IPv6 server_name domain1.com; location / { proxy_pass http://backend1:8080/; } } server { listen 80; listen [::]:80; server_name domain2.com; location / { proxy_pass http://backend2:8080/; } }}```
gollark: The reverse-proxy solution is in my opinion the best one, although it would require some config.
gollark: I think LetsEncrypt may not be very happy with that, though.
gollark: Yes, and you can just use a reverse proxy (with "vhosts" or whatever) for that, easy enough.
gollark: I think those are just what some webservers call "doing different things based on the host header".

See also

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.