Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

No checks for validity of an application name #54

Open
bg6954 opened this issue Aug 23, 2013 · 1 comment
Open

No checks for validity of an application name #54

bg6954 opened this issue Aug 23, 2013 · 1 comment

Comments

@bg6954
Copy link

bg6954 commented Aug 23, 2013

There seems to be no checks in place for application name, invalid application name is initially accepted with a successful push and start but no way to access the URL.

$ cf push --command "node nodejsHelloworld.js"
Name> nodejsHelloworld0.0.1

Save configuration?> n

Uploading nodejsHelloworld0.0.1... OK

nodejsHelloworld0.0.1 is currently stopped, start it with 'cf start'

$ cf start nodejsHelloworld0.0.1
Preparing to start nodejsHelloworld0.0.1... OK
Checking status of app 'nodejsHelloworld0.0.1'...
5 of 5 instances running (5 running)
Push successful! App 'nodejsHelloworld0.0.1' available at http://.

@xoebus
Copy link

xoebus commented Aug 30, 2013

Agreed, app names/subdomains should be validated in a way that gives better info back to the user rather than just not starting the app.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants