ASP.NET/IIS with SSL/HTTPS login redirect not working from..

When you try to get to a secure page while accessing the site from the
Internet it redirects you to the login page. You type the username/password
and hit login and it just comes back to the login page again without getting
redirected. The custom authentication is not the problem as when you do this
from the LAN side using the external IP address the username/password logins
and redirects you to the secure page.

Hope this helps clear it up a bit.

Cheers,

Akshay Srinivasan
--
Life is about joy!


"David Wang" wrote:

> Please define what "not working" means. Does the redirection never
> happen, redirects to the wrong IP Address, or ???
>
> If it works in LAN but not WAN and you are using custom authentication,
> that's usually an issue with your application's interaction with WAN
> and not an issue with IIS. You're really asking about bugs in either
> your network configuration or your application - so please describe
> both of them better.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>
>
> Akshay Srinivasan wrote:
> > Hi,
> >
> > I have IIS setup for HTTPS on Windows 2003 Server on a LAN connected to the
> > internet. I have port forwarding on the router to forward ports 80 and 443.
> > When I access the login page on the LAN it works when I access it from the
> > WAN through the same router it gets to the login page but never redirects to
> > the page that called the login page. For example I type
> > https://1.1.1.1/Secure/somepage.aspx which then calls the login.aspx page.
> > It pops up the login page https://1.1.1.1/Login.aspx. ; You enter the same
> > login and password that you do on the LAN and it seems to fail and never
> > redirects to the Secure/somepage.aspx. Please tell me if you have any idea
> > why this would be. 1.1.1.1 is the IP address of the router in this example
> > which is a valid static IP address.
> >
> > Cheers,
> >
> > Akshay Srinivasan
> >
> > --
> > Life is about joy!
>
>
 >> Stay informed about: ASP.NET/IIS with SSL/HTTPS login redirect not working from.. 

I had the same problem, I found that it was because I had
<%transaction=required%> on the asp page I was redirecting to.

It only seams to be a problem on a windows 2003 machine ( connecting to
or from another machine).

That statement seams to shut down IIS.

On Jan 25, 8:18 pm, Akshay Srinivasan
<AkshaySriniva....RemoveThis@discussions.microsoft.com> wrote:
> When you try to get to a secure page while accessing the site from the
> Internet it redirects you to the login page. You type the username/password
> and hit login and it just comes back to the login page again without getting
> redirected. The custom authentication is not the problem as when you do this
> from the LAN side using the external IP address the username/password logins
> and redirects you to the secure page.
>
> Hope this helps clear it up a bit.
>
> Cheers,
>
> Akshay Srinivasan
> --
> Life is about joy!
>
>
>
> "David Wang" wrote:
> > Please define what "not working" means. Does the redirection never
> > happen, redirects to the wrong IP Address, or ???
>
> > If it works in LAN but not WAN and you are using custom authentication,
> > that's usually an issue with your application's interaction with WAN
> > and not an issue with IIS. You're really asking about bugs in either
> > your network configuration or your application - so please describe
> > both of them better.
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //
>
> > Akshay Srinivasan wrote:
> > > Hi,
>
> > > I have IIS setup for HTTPS on Windows 2003 Server on a LAN connected to the
> > > internet. I have port forwarding on the router to forward ports 80 and 443.
> > > When I access the login page on the LAN it works when I access it from the
> > > WAN through the same router it gets to the login page but never redirects to
> > > the page that called the login page. For example I type
> > >https://1.1.1.1/Secure/somepage.aspxwhich then calls the login.aspx page.
> > > It pops up the login pagehttps://1.1.1.1/Login.aspx. ; You enter the same
> > > login and password that you do on the LAN and it seems to fail and never
> > > redirects to the Secure/somepage.aspx. Please tell me if you have any idea
> > > why this would be. 1.1.1.1 is the IP address of the router in this example
> > > which is a valid static IP address.
>
> > > Cheers,
>
> > > Akshay Srinivasan
>
> > > --
> > > Life is about joy!- Hide quoted text -- Show quoted text -
 >> Stay informed about: ASP.NET/IIS with SSL/HTTPS login redirect not working from.. 

Thanks for the tip but I searched my entire site and there is no reference
even to the word transaction on an page even in VS 2005 and not searching the
compiled stuff. If you have any other ideas please shoot.

Cheers,

Akshay Srinivasan

--
Life is about joy!


"joej45@yahoo.com" wrote:

> I had the same problem, I found that it was because I had
> <%transaction=required%> on the asp page I was redirecting to.
>
> It only seams to be a problem on a windows 2003 machine ( connecting to
> or from another machine).
>
> That statement seams to shut down IIS.
>
> On Jan 25, 8:18 pm, Akshay Srinivasan
> <AkshaySriniva....RemoveThis@discussions.microsoft.com> wrote:
> > When you try to get to a secure page while accessing the site from the
> > Internet it redirects you to the login page. You type the username/password
> > and hit login and it just comes back to the login page again without getting
> > redirected. The custom authentication is not the problem as when you do this
> > from the LAN side using the external IP address the username/password logins
> > and redirects you to the secure page.
> >
> > Hope this helps clear it up a bit.
> >
> > Cheers,
> >
> > Akshay Srinivasan
> > --
> > Life is about joy!
> >
> >
> >
> > "David Wang" wrote:
> > > Please define what "not working" means. Does the redirection never
> > > happen, redirects to the wrong IP Address, or ???
> >
> > > If it works in LAN but not WAN and you are using custom authentication,
> > > that's usually an issue with your application's interaction with WAN
> > > and not an issue with IIS. You're really asking about bugs in either
> > > your network configuration or your application - so please describe
> > > both of them better.
> >
> > > //David
> > >http://w3-4u.blogspot.com
> > >http://blogs.msdn.com/David.Wang
> > > //
> >
> > > Akshay Srinivasan wrote:
> > > > Hi,
> >
> > > > I have IIS setup for HTTPS on Windows 2003 Server on a LAN connected to the
> > > > internet. I have port forwarding on the router to forward ports 80 and 443.
> > > > When I access the login page on the LAN it works when I access it from the
> > > > WAN through the same router it gets to the login page but never redirects to
> > > > the page that called the login page. For example I type
> > > >https://1.1.1.1/Secure/somepage.aspxwhich then calls the login.aspx page.
> > > > It pops up the login pagehttps://1.1.1.1/Login.aspx. ; You enter the same
> > > > login and password that you do on the LAN and it seems to fail and never
> > > > redirects to the Secure/somepage.aspx. Please tell me if you have any idea
> > > > why this would be. 1.1.1.1 is the IP address of the router in this example
> > > > which is a valid static IP address.
> >
> > > > Cheers,
> >
> > > > Akshay Srinivasan
> >
> > > > --
> > > > Life is about joy!- Hide quoted text -- Show quoted text -
>
>
 >> Stay informed about: ASP.NET/IIS with SSL/HTTPS login redirect not working from.. 

We've had this one, too. We had to reset the connections on the firewall.

We run an asp.net app and I get a call that nothing works over SSL. Investigating this, I make an https request (for foo.gif in the root dir, which actually exists) to IIS by internal IP inside the firewall. Presto...it works! Make the same request from outside and it fails (404). doh!

Then, netmon (network monitor) reveals that the connection is established, but then just sort of dies. The firewall seemed the next logical stop.

So, my network guy tells me that the firewall's connection list appears to have become full/corrupt...? Now, hopefully a little research and testing and we can squash this in the future. Anyway, after resetting the connections on the firewall, our little pandora's box of a problem had been remedied.

I post this because of the vast amount of unresolved threads I found complaining of SSL over IIS/ASP.NET failing. That said, I would encourage that if you are having trouble and your cert is good, IIS properly configured (i.e. the app and you have a baseline of good, healthy, unit-tested results)...then perhaps rule out IIS first with a simple test like that above. If IIS is good then the network likely holds the key. In that case pulling the packets off the wire should reveal more information as to the location of the issue.

Of course, I use the term "remedied" rather than solved because this type of issue has many faces, requiring any number of solutions. For example, our issue involved the failure of graceful redirects to https, not response encoding via asp.net or forced redirects outside asp.net. Anyway, my sandwich is now gone. I hope someone finds this useful.
 >> Stay informed about: ASP.NET/IIS with SSL/HTTPS login redirect not working from..