Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

504 for https #27

Open
Uncle-Bens opened this issue Apr 5, 2017 · 5 comments
Open

504 for https #27

Uncle-Bens opened this issue Apr 5, 2017 · 5 comments

Comments

@Uncle-Bens
Copy link

Uncle-Bens commented Apr 5, 2017

Hi!
I use prerender on my own server and have
respond 504 for https and 200 for http.
prerender 504 edited

Could you please help.

@thoop
Copy link
Contributor

thoop commented Apr 5, 2017

Which version of this middleware are you using? That bug should have been fixed a long time ago:

b11ebec

Can you update to the latest code?

@jaandrews
Copy link

jaandrews commented Apr 28, 2017

I'm encountering this issue as well. I currently have 1.0.0.2 installed via nuget. Maybe there's an issue with the nuget package? I checked the code in the repository and it looks correct.

@thoop
Copy link
Contributor

thoop commented Apr 28, 2017

I think the nuget package hasn't been updated in a long time. Can you post a link to that repository so we can take a look?

@jaandrews
Copy link

jaandrews commented Apr 28, 2017

Sorry I wasn't clear enough. What I meant was that I checked the Prerender_asp_mvc repository to confirm that the old code hadn't somehow found its way back in (it hadn't).

I tried installing the nuget package in a new project and confirmed that the dll is too old. Here is a screen shot of the dll added by the nuget package.
prerender-issue
The dll was last modified 6/30/14, which would be before the fix was in place.

I should be able to get around this by pulling it down and building it myself, so this isn't an urgent issue for me, but it would be nice to have the nuget package up to date.

@thoop
Copy link
Contributor

thoop commented Apr 28, 2017

Sorry about that! I think that nuget package was uploaded by a random person and we haven't been able to get in touch with them. We might have to upload an official one under a different name.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants