As a Rebrandly engineer,
I need to verify that a given domain connected to Rebrandly is indeed connected to Rebrandly at application layer,
So that I can verify that the aliasing is active for this domain name and mark it as verified.
Acceptance Tests
Given a domain DOMAIN where a server using this middleware is running,
When I navigate http://DOMAIN/.well-known/rebrandly route,
Then I get a textual (text/html) response stating "Rebrandly was here"
Given a domain DOMAIN where a server which is not using this middleware is running,
When I navigate http://DOMAIN/.well-known/rebrandly route,
Then I do not get a response stating "Rebrandly was here" (I got nothing, or something else)
User Stories
As a Rebrandly engineer,
I need to verify that a given domain connected to Rebrandly is indeed connected to Rebrandly at application layer, So that I can verify that the aliasing is active for this domain name and mark it as verified.
Acceptance Tests
Given a domain DOMAIN where a server using this middleware is running, When I navigate http://DOMAIN/.well-known/rebrandly route, Then I get a textual (
text/html) response stating "Rebrandly was here"Given a domain DOMAIN where a server which is not using this middleware is running, When I navigate http://DOMAIN/.well-known/rebrandly route, Then I do not get a response stating "Rebrandly was here" (I got nothing, or something else)