network profile
| bio | website | |
|---|---|---|
| location | ||
| age | 28 | |
| visits | member for | 4 months |
| seen | Jan 15 at 19:02 | |
| stats | profile views | 1 |
Sofware enthusiastic and apprentice python wizard.
|
Jan 9 |
awarded | Editor |
|
Jan 9 |
comment |
BrowserID and HTTPS conflict? I updated the question with more information. This question will expose more of my ignorance but by client your referring to my webapp which i deployed with heroku right? |
|
Jan 9 |
revised |
BrowserID and HTTPS conflict? more information |
|
Jan 9 |
comment |
BrowserID and HTTPS conflict? @D.W Your probable being very clear to someone isn't very new to web development like me. I'm unsure how to force the client to make the request over HTTPS in the first place. I thought that was the purpose of the restricting /redirecting that happens in said extension. |
|
Jan 9 |
comment |
BrowserID and HTTPS conflict? @D.W I believe thats what the extension i linked is achieving. I believe it doesn't allow http connections with say the heroku routing layer. |
|
Jan 9 |
awarded | Student |
|
Jan 9 |
comment |
BrowserID and HTTPS conflict? I'm deploying on heroku so and it seems they heroku sets the port on "the backend". Is there another way to test this? Thanks. |
|
Jan 8 |
asked | BrowserID and HTTPS conflict? |
