summaryrefslogtreecommitdiff
path: root/src/server/RunHTTP.hs
AgeCommit message (Collapse)Author
2013-06-13Fix UTF-8 decoding problem in gf -serverhallgren
The package network-2.4.1.1 thoughlessly introduced a backward incompatible change to the function Network.URI.unEscapeString, see https://github.com/haskell/network/commit/f2168b1f8978b4ad9c504e545755f0795ac869ce This also affects the function Network.Shed.Httpd.queryToArguments, which is used in GFServer.hs. To remain compatible with older and newer versions of the network package, we need to stay clear of queryToArguments and unEscapeString. A replacement function has been added to server/URLEncoding.hs.
2011-10-10More functionality in "gf -server" modehallgren
"gf -server" mode now includes PGF service and the services to support example-based grammar writing. (But gf -server is not quite ready to replace pgf-http yet...) Also bumped GF version number to 3.2.10-darcs
2011-08-25pgf-http: fix a bug that caused "+" to be treaded as " " in PGF service ↵hallgren
requests URLs. This was a bug in my workaround for a bug in the httpd-shed package. It made it impossible to use the glue token "&+" for Turkish input in the minibar, for example.
2010-12-17RunHTTP.hs: remove hardcoded document roothallgren
The document root is now part of the arguments passed to runHTTP.
2010-09-10pgf-server HTTP mode: support the Accept-Language headerhallgren
It is needed for the userLanguage field in the grammar info from pgf-server
2010-09-03pgf-server HTTP mode: workaround for bugs in the httpd-shed package that ↵hallgren
prevented the fridge and translate web apps from working queryToArguments "?&input=bla+bla" returns [("&input","bla+bla")] but should return [("input","bla bla")]
2010-09-01Standalone HTTP version of pgf-serverhallgren
pgf-server can now act as a standalone HTTP server. To activate this mode, start it with pfg-server http to use the default port number (41296), or give an explicit port number, e.g., pgf-server http 8080 The HTTP server serves PGF files in the same way as the old FastCGI interface. In addition, it also serves static files. The document root for static files is the www subdirectory of the current directory where pgf-server is started. In spite of these addition, backwards compatibility is maintaned. The old FastCGI interface continues to work as before. (It is activated when pgf-server is started without arguments.)