Jump to content

Make URL-encoding smarter or optional


Recommended Posts

Ref: http://www.alfredforum.com/topic/5993-custom-searches-with-full-url-as-the-query/

Unless {query} is the entire URL, the Open URL action behaves as if {query} is a query string value and URL-encodes it, i.e. it assumes:

http://www.example.com/page?arg={query}

This is not always the case, however. {query} may also be a part of the URL path, e.g.

http://www.example.com/{query}/some/other/thing

In the latter case, most browsers will choke on the URL (I think only Firefox is smart enough to handle URL-encoded paths).

Alfred should ideally provide a checkbox to turn URL-encoding of {query} off to avoid messing up {query}.

Alternatively, it could try to determine whether {query} is actually the value of a GET parameter (for example, based on the presence of "arg=…"), but the on/off option is probably more robust.

Edited by deanishe
Link to comment
Share on other sites

I agree, there are definitely improvements which can be made in this area, but I may leave this until a more major release (as there is the Workflows workaround at this point).

 

Other improvements would be the option to encode spaces as other characters such as - and _ which would give even more flexibility.

 

I've added a ticket :)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...