• Instructions to Ask a Question

    For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.

    We offer seven comprehensive applications designed to help you efficiently manage and grow your business:

    Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.

    🚀 Exclusive Lifetime Offers 🚀

    We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:

    • 🔥 Pabbly Connect — Lifetime Access for $249View Offer
    • 🔥 Pabbly Subscription Billing — Lifetime Access for $249View Offer

    Make a one-time investment and enjoy the advantages of robust business management tools for years to come.

BUG: Pabbly doesn't escape URLs _at all_

solipsist

Member
I used Email Parser to extract an attachment but neither CloudConvert nor Dropbox (upload file) can access it. After looking at cases where this did work, my conclusion is that Pabbly doesn't escape spaces in URLs correctly escape URLs at all.

This requires an immediate fix.

This was an attempt to use CloudConvert to rename the file to something non-offending... doesn't work.

1638640107461.png
 
Last edited:

solipsist

Member
Confirmed.

I added a Text Formatter Replace step that replaced {{space}} with "%20" and Dropbox upload file works.

Please test your software!
 

solipsist

Member
Turns out it doesn't escape anything as characters like å and ø also results in Dropbox failing due to being passed a misformed URL.

The workaround is to use Text Formatter instead. Still, it's an unnecessary step that shouldn't be needed.

1638736455423.png
 
Last edited:
P

Pabblymember11

Guest
Hey @solipsist

It seems like you have already solved your concern. So could you please confirm that the above workflow is working?

Further, if not then kindly let us know.

Thanks
 

solipsist

Member
Yes, by deleting the leading "http://", encoding the string and then prefixing it with http:// again... ugly. It's a workaround. Not a proper solution. It adds two unnecessary workflow steps. You need to pass properly escaped URLs to the services you integrate with.
 
Top