 
|
| Sender: |
|
| Date: |
Tue, 4 May 2010 12:10:38 -0600 |
| Content-Disposition: |
inline |
| Reply-To: |
|
| Message-ID: |
<11157F498B3744E0095E4EF6@[192.168.1.100]> |
| Content-Transfer-Encoding: |
7bit |
| Subject: |
|
| From: |
|
| Content-Type: |
text/plain; charset=us-ascii; format=flowed |
| In-Reply-To: |
|
| MIME-Version: |
1.0 |
| Comments: |
|
I'd be inclined to blame your webserver...not 100% sure, but I'm 90% sure
that it's the webservers responsibility to decode URL GET arguments before
passing them onto the CGI client.
--On Tuesday, May 04, 2010 1:40 PM -0400 "Kaminsky,Matthew"
<[log in to unmask]> wrote:
> We've run into a little quirk with Listserv 15.5 UNIX, and I'm not sure
> where to fix it. One listowner has some subscribe requests coming in,
> and they're being forwarded to him just fine, handy dandy URL encoded
> link to subscribe the person ready to go. However, when they hit the
> link, and listserv reads in the command, it doesn't perform any URL
> decoding and tacks on our domain at the end of the whole URL encoded
> address. I'm not sure where the decoding is failing to happen, anyone
> have any pointers?
|
|
|
