[privoxy-devel] [ ijbswa-Bugs-1587194 ] 3.0.5 shortcut doesn't allow spaces in config file path

[SourceForge.net <no...@so...>]

Bugs item #1587194, was opened at 2006-10-30 13:16
Message generated for change (Comment added) made by proactivesvcs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=111118&aid=1587194&group_id=11118

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: windows-specific
Group: version 3.0
>Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Adam Piggott (proactivesvcs)
Assigned to: Fabian Keil (fabiankeil)
Summary: 3.0.5 shortcut doesn't allow spaces in config file path

Initial Comment:
Using 3.0.5 release on Windows 2000 SP4.

I start Privoxy with a shortcut to the following:
"D:\Program Files\Privoxy\privoxy.exe"
%userprofile%\Application Data\Privoxy\config.txt

This worked fine in 3.0.3. In 3.0.5 Privoxy does not
parse the spaces correctly and tries to open
Data\Privoxy\config.txt.

I should probably have enclosed the file name with
quotes, but since it used to work I figured I should
file a report :-)

----------------------------------------------------------------------

>Comment By: Adam Piggott (proactivesvcs)
Date: 2006-10-30 18:49

Message:
Logged In: YES 
user_id=1611181

> The white space parsing isn't done by Privoxy. Privoxy is
supplied with a list of arguments and only has to
> recognise them.

That's what I thought, however...I replaced privoxy.exe,
standard.action and default.action with Privoxy 3.0.3. I
execute it from a shortcut with no quotes in the config
parameter and it works successfully. I checked that the log
entry which specifies the config file is correct, which it is.

I replace the three files with 3.0.5 and get the described
error. Once the quotes are included, it fires up fine.

----------------------------------------------------------------------

Comment By: Fabian Keil (fabiankeil)
Date: 2006-10-30 15:49

Message:
Logged In: YES 
user_id=875547

The white space parsing isn't done by Privoxy.
Privoxy is supplied with a list of arguments
and only has to recognise them.

If you don't escape the white space in the
configfile (or put it in quotes), Privoxy
gets it delivered as two separate arguments.

As you noticed, Privoxy then interprets the last
argument as configfile.

To make it behave the way you described it, Privoxy
would have to merge different arguments together
again. As far as I can see, this wasn't done in
Privoxy 3.0.3 either.

Did you verify this with the exact same OS and
under the exact same circumstances? Maybe you started
Privoxy 3.0.3 slightly different and Windows
used some argument parsing magic.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=111118&aid=1587194&group_id=11118