Proxy service down since builder update

[Bruce Stuart]

Will the old solution fix the issue that I reported 2 weeks ago, where a message of over 2k won't go through the old proxy ?

[Illya Stepanov]

@Shaun - Yes, that's correct you can use old proxy in your app and it won't prevent our investigation.

@Bruce - Can't tell you for sure now, we need to test it.

[Shaun7189763]

Thanks Illya. I will use the old proxy setting and wait for the result of your investigation.
Best regards,
Shaun

[Bruce Stuart]

1. Using the old proxy implementation fixes my errors.
   1. Neither using the old proxy or the 'new proxy' produces errors on my email thread that Yurri was working with me on - I'll update that thread instead of burdening this thread.

[Illya Stepanov]

Hi Shaun -

Sending username and password via URL is not secure.
Therefore this format is no longer supported by either IE or Chrome:
http://support.microsoft.com/kb/834489
https://code.google.com/p/chromium/is...

It's better to use Basic or Digest Authentication:
http://tools.ietf.org/html/rfc2617

You will need to remove login/password from URL and move it into header like it means for basic auth.

[Shaun7189763]

Hello Illya,

So, if I understand this correctly, it means that using the Twillio API is not possible anymore as their rest api request should be build as follows:

https://{AccountSid}:{AuthToken}@api....

(http://www.twilio.com/docs/api/rest/r...)

The same applies to Mailgun API (cf. http://documentation.mailgun.com/api-...)

Can you confirm that using the Twilio API and the Maigun API is not possible with the new proxy implementation? Or is there a solution?

Thanks,

Shaun

[Illya Stepanov]

Hi Shaun -

Let me explain it with more details --
In general to authorize in these services (twilio, mailgun) is used HTTP basic auth.

You can use it in a 2 ways:

1. Set the 'username: password' in the URL, eg: http://user:pass@some.service.com

2. Set the header Authorization, like described here: http://devcenter.appery.io/documentat...

   The old proxy -- tooks data from #1 and converted it into #2, the new proxy implementation does not!
   Thus, it is enough to remake the service to use option #2, and it will work with the new proxy.

   To make secure proxy work, you need to write into the database already encoded content of Authorization header and in the service in the value field to point something like: 'Basic {auth_data}'

   You can also look here: http://devcenter.appery.io/documentat...

[Shaun7189763]

Illya,

Thank you so much.
I've followed your instructions and that of http://devcenter.appery.io/documentat... . It's now working like a charm!

Great!