**Use case**
ClickHouse as a web server becomes a viable scenario.
(At least in backoffice).

**Describe the solution you'd like**
Add this field.

**Additional context**
It's in question how to name it. The original HTTP specs has the famous typo in it and name it `referer`. While JavaScript has this typo fixed and name it `referrer`.

in_post_maybe_compressed = std::move(in_post);
    std::unique_ptr<ReadBuffer> in;
    static const NameSet reserved_param_names{"compress", "decompress", "user", "password", "quota_key", "query_id", "stacktrace",
        "buffer_size", "wait_end_of_query", "session_id", "session_timeout", "session_check"};
    Names reserved_param_suffixes;
    auto param_could_be_skipped = [&] (const String & name)
    {
        
        if (name.empty())
            return true;
        if (reserved_param_names.count(name))
            return true;
        for (const String & suffix : reserved_param_suffixes)
        {
            if (endsWith(name, suffix))
                return true;
        }
        return false;
    };
    
    
    
    
    
    
    
    
    
    const auto & settings = context.getSettingsRef();