Port not being mapped on HTTP request

[CodeGenie1]

I have several parse instances running on different ports. When trying to connect to an instance that is not on the default port, all requests fail. It appears that the port number is not being mapped into the HTTP url request. e.g in parse_user.dart login method:

      Uri url = Uri(
          scheme: tempUri.scheme,
          host: tempUri.host,
          path: "${tempUri.path}$keyEndPointLogin",
          queryParameters: {
            keyVarUsername: username,
            keyVarPassword: password
});

Amending this to pass in the port fixes the problem:-
      Uri url = Uri(
          scheme: tempUri.scheme,
          host: tempUri.host,
          **port: tempUri.port,**
          path: "${tempUri.path}$keyEndPointLogin",
          queryParameters: {
            keyVarUsername: username,
            keyVarPassword: password
});

There are several instances in the code where this will need a fix. (parse_user, parse_object etc.)

[phillwiggins]

Hey Good idea. I overlooked that scenario. Are you happy to do the work and create a PR or would you like me to for the next version?

…

On Thu, Mar 7, 2019, 11:48 CodeGenie1 ***@***.***> wrote: I have several parse instances running on different ports. When trying to connect to an instance that is not on the default port, all requests fail. It appears that the port number is not being mapped into the HTTP url request. e.g in parse_user.dart login method: Uri url = Uri( scheme: tempUri.scheme, host: tempUri.host, path: "${tempUri.path}$keyEndPointLogin", queryParameters: { keyVarUsername: username, keyVarPassword: password }); Amending this to pass in the port fixes the problem:- Uri url = Uri( scheme: tempUri.scheme, host: tempUri.host, **port: tempUri.port,** path: "${tempUri.path}$keyEndPointLogin", queryParameters: { keyVarUsername: username, keyVarPassword: password }); There are several instances in the code where this will need a fix. (parse_user, parse_object etc.) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#101>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgn3o1DzWSsOFhK7plks60dKNZUfHUmks5vUPyEgaJpZM4bjAL3> .

[RodrigoSMarques]

Hello, CodeGenie1.

I also use Parse Server on ports other than the default.

I have 3 applications on the same server and each on your port.

I use Nginx to do the redirect of the endpoint/url to the respective port.

[phillwiggins]

It's a similar setup my side too. Nginx & Docker working together to direct traffic via sub domains. I do think the ability to add ports might solve people's issues who don't have that technical ability or access to quickly hook up their client to server.

…

On Thu, Mar 7, 2019, 12:06 Rodrigo de Souza Marques < ***@***.***> wrote: Hello, CodeGenie1. I also use Parse Server on ports other than the default. I have 3 applications on the same server and each on your port. I use Nginx to do the redirect of the endpoint/url to the respective port. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#101 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgn3skR_QPSxBNnHKoGXjzjDLh--RjXks5vUQDbgaJpZM4bjAL3> .

[CodeGenie1]

Hi Phill,
I hope you don't mind me leaving this one with you for the next release. I'm still learning Flutter\dart\Git, having done C#/WPF enterprise and subversion most of my career !. I'm working with a colleague to convert an exising Android App to Flutter Dart, and it uses Parse, hence my interest. Have most of the Parse stuff working fine, so many thanks for developing the library.

[phillwiggins]

That's fine. I'm pretty swamped myself so can't promise you a release date but I will ensure it's in the next release for you. I'll comment on this thread when done. Cheers

…

On Thu, 7 Mar 2019 at 16:01, CodeGenie1 ***@***.***> wrote: Hi Phill, I hope you don't mind me leaving this one with you for the next release. I'm still learning Flutter\dart\Git, having done C#/WPF enterprise and subversion most of my career !. I'm working with a colleague to convert an exising Android App to Flutter Dart, and it uses Parse, hence my interest. Have most of the Parse stuff working fine, so many thanks for developing the library. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#101 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgn3miDLt1dmRIQtVzrGF0np95TR0Ozks5vUTe9gaJpZM4bjAL3> .

-- Kind Regards Phill Wiggins Phill.Wiggins@Gmail.com

[phillwiggins]

This has been fixed in version 1.0.16. This will be released shortly.