• Instructions to Ask a Question

    Click on the "Ask a Question" button and select the application for which you would like to ask questions.

    We have 5 different products namely - Pabbly Connect, Pabbly Subscription Billing, Pabbly Email Marketing, Pabbly Form Builder, Pabbly Email Verification.

    The turnaround time is 24 hrs (Business Hours - 10.00 AM to 6.00 PM IST, Except Saturday and Sunday). So your kind patience will be highly appreciated!

    🚀🚀Exclusive Discount Offer

    Just in case you're looking for any ongoing offers on Pabbly, you can check the one-time offers listed below. You just need to pay once and use the application forever -
     

    🔥 Pabbly Connect One Time Plan for $249 (🏆Lifetime Access) -  View offer 

    🔥 Pabbly Subscription Billing One Time Plan for $249 (🏆Lifetime Access) - View offer

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:

Supreme

Well-known member
Staff member
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