I am working on wicket version 1.4.17 in my application with tomcat 7.
After updating tomcat my application is broken.
The login page is not working when submit is clicked. It is working when I hit enter in the url.
If I click on the login button it is returning the same page, but if I login again then it is working.
Your problem might be related to Tomcat changing the session id after login.
Hard to tell whether your code or Wicket can't handle it, but 1.4.x is discontinued already.
Related
I have a project in Ionic 4, when I do ionic serve it runs at localhost:8100/
Now when it loads home page, the URL is localhost:8100/home, if I open contact page the URL becomes localhost:8100/contact.
When I try to copy the above URL and hit, then it says -
Sorry, this page doesn't exist. Please check the URL or go back a page.
What do I need to do to get this working?
Based on your comments this is happening because your server does not support fallback. So when you enter a url manually, the server is trying to find that page, but you only have index.html in your app because of Client side routing.
If the app uses the Angular router, you must configure the server to
return the application's host page (index.html) when asked for a file
that it does not have.
The configuration is specific to your server or cloud platform. You can check Angular deployment for more info.
This regularly should not happen and you can't do anything for this. Try to upgrade your ionic to the latest with nodejs since the error my be from currupted project creation. Then after update create a new project and it should go good.
Anyway I can custom Jboss EAP 7 management console login page by adding Log-on Warning Banner in it?
HAL is protected by digest authentication. And as such the browser takes care of the login. Bottom line you won't be able to customize the login.
HAL is the project behind the web console in WildFly: https://hal.github.io/
You can customize it there with extensions (i don't really know the details)
I've installed the community version of DNN.
then i've started to develop some modules - this worked fine.
then i saw that dnn have AuthenticationServices and wanted to create one for connection to MS CRM.
then i've tried to install this AuthenticationServices and it worked. After that i wasn't able to login to the host anymore. i keep getting the error: ERR_TOO_MANY_REDIRECTS.
bevor i've started with changes i cloud login with dnndev.me/admin or dnndev.me/host.
dnndev.me/admin get redirected to my custom login page.
And dnndev.me/host gets me an ERR_TOO_MANY_REDIRECTS error.
is there an easy way to repair this? or do you prefer to reinstall dnn?
It looks like when you try to login into DotNetNuke it will add the login module to the home/start site into the ContentPane.
Unfortunately i changed the template, with one that didn't have the ContentPane. So you can't access with the link dnndev.me/admin.
For access via dnndev.me/host, I'm not quite sure if it was the same problem.
I solved everything with a new clean install.
and a little hint:
i'm now create a master login page like masterlogin and put the account login module on it.
now i should be able to login whenever an error occur.
I am also trying to deploy a ZendSkeletonApplication on a shared host but I am facing some problem regarding redirection. The problem is when a user try to login it gets stuck to /projectname/user/authenticate. It doesn't get redirected to dashboard after authentication.Unfortunately all i see is a white, empty page. Locally it worked perfectly Here it looks like Zend doesn't recognize that it should do anything with this url and redirecto to appropriate action.
Thanks in advance
The problem is presented by the new release of PHP. Try updating your version of php above 3.xx. I upgraded to the latest version of php in the hosting and the problem was solved. PHP 5
I am developing a Facebook application and I am using Facebook C# SDK v4.2.1 to help with authentication. I am building the application using ASP.NET MVC 2 and am hosting it in Windows Azure (SDK v1.2).
Everything has been running fine when I had my application in a full browser window, but now when I am attempting to IFrame it in Facebook, I run into session problems. The behavior is that a new session is created on every new page request so the user always comes back to the application's login page. I can see that that Facebook session is valid when Facebook redirects back to the application after authorization, but when I set some session variables and redirect to another page, the session is gone.
When I debug the application locally, both as a standalone web application and in the Development Fabric, everything works fine. It is only when it's published to Azure that I get the problems. I have tried to have a local debug environment that is very similar to production where I have the facebook application at apps.facebook.com/myappnamedev that points to localhost on a specific port.
I just now also discovered that I only see the problem in IE (I am using v.8). Firefox v3.6 and Safari v.5 works fine.
Any ideas to help my troubleshooting? I have spent 10 hours on it and it's getting really frustrating... I am happy to paste code/configuration info if needed, just let me know.
Thank you in advance!
// Peter
I solved this. The redirect from Facebook after authentication landed on different pages in my development environment compared when deployed to Azure. I moved my authentication logic to global.asax instead.