| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Donald Fraser" <postgres(at)kiwi-fraser(dot)net>, "[BUGS]" <pgsql-bugs(at)postgresql(dot)org>, "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su>, "Teodor Sigaev" <teodor(at)sigaev(dot)ru> |
| Subject: | Re: Bug with Tsearch and tsvector |
| Date: | 2010-04-27 14:22:24 |
| Message-ID: | 4BD6ACD00200002500030E5C@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> We'd probably not want to apply this as-is, but should first
> tighten up what characters URLPath allows, per Kevin's spec
> research.
If we're headed that way, I figured I should double-check. The RFC
I referenced was later obsoleted by:
http://www.ietf.org/rfc/rfc3986.txt
I haven't been able to find anything more recent. This newer RFC
doesn't seem to list characters which are *not* part of a URI, so
here are the characters which *are* allowed:
gen-delims = ":" / "/" / "?" / "#" / "[" / "]" / "@"
sub-delims = "!" / "$" / "&" / "'" / "(" / ")"
/ "*" / "+" / "," / ";" / "="
unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"
I'll read this RFC closely and follow up later today.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-04-27 14:32:12 | Re: Bug with Tsearch and tsvector |
| Previous Message | Tom Lane | 2010-04-27 03:32:19 | Re: Bug with Tsearch and tsvector |