cgit/ui-shared.c, branch v0.8

ui-shared: add cgit_tag_link()

2008-10-05T19:18:45Z

This function can be used to generate properly escaped links to the tag page. Signed-off-by: Lars Hjemli

ui-shared: generate proper links in cgit_object_link()

2008-10-05T19:12:08Z

Signed-off-by: Lars Hjemli

ui-shared: use html_url_path() to get properly escaped url in form action

2008-10-05T17:25:47Z

When a repo uses an url with e.g. '#' or '?' characters this needs to be properly escaped when used as action in a form tag. Signed-off-by: Lars Hjemli

ui-shared: reword the standard page footer

2008-10-05T17:09:58Z

Signed-off-by: Lars Hjemli

ui-shared: do not print repo name on the "summary" tab

2008-10-05T17:00:32Z

Signed-off-by: Lars Hjemli

ui-repolist + ui-shared: Use cgit_summary_link()

2008-10-05T15:16:36Z

This makes is possible to use cgit with repository urls containing special url characters like '#' and '?'. Signed-off-by: Lars Hjemli

ui-shared.c: add cgit_summary_link()

2008-10-05T14:55:50Z

This function can be used to generate a link to the summary page for the currently active repo. Signed-off-by: Lars Hjemli

ui-shared.c: use html_url_path() in repolink()

2008-10-05T14:54:44Z

This makes sure that reponames and paths are properly escaped when used as urls. Signed-off-by: Lars Hjemli

ui-shared.c: use html_url_arg()

2008-10-05T10:52:25Z

The link-generating functions are updated to use the new html_url_arg function, thereby fixing links to strange repos, branches and files. Also, the test-suite is updated to verify some cases of strange urls. Signed-off-by: Lars Hjemli

use Host: header to generate cgit_hosturl

2008-09-01T23:26:37Z

I run an instance of lighttpd for cgit behind nginx (nginx doesn't execute CGI). So the port (SERVER_PORT=33333) that lighttpd runs on sends to cgit is different from the standard port 80 that public clients connect to (via nginx). This was causing the Atom feed URL to show the private port number that lighttpd was running on. Since the HTTP/1.1 "Host" header includes the port number if running on a non-standard port, it allows non-client-facing HTTP servers to transparently generate public URLs that clients can see. So use the "Host" header if it is available and fall back to SERVER_NAME/SERVER_PORT for some clients that don't set HTTP_HOST. Signed-off-by: Eric Wong