You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2020/08/24 14:47:42 UTC

[GitHub] [apisix-dashboard] liuxiran opened a new issue #396: [question]got error after login

liuxiran opened a new issue #396:
URL: https://github.com/apache/apisix-dashboard/issues/396


   Please answer these questions before submitting your issue.
   
   - Why do you submit this issue?
   - [ ] Question or discussion
   - [ ] Bug
   - [ ] Requirements
   - [ ] Feature or performance improvement
   - [ ] Other
   
   ___
   ### Question
   - What do you want to know?
   I pull the latest code, and run docker component
   after I login from login page , I got two errors:
   
   ![image](https://user-images.githubusercontent.com/2561857/91050972-055e6300-e652-11ea-8c71-e91e1015f2f6.png)
   
   ___
   ### Bug
   - Which version of Apache APISIX Dashboard, OS and Broswer?
   
   - What happened?
   If possible, provide a way to reproduce the error.
   
   ___
   ### Requirement or improvement
   - Please describe your requirements or improvement suggestions.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-dashboard] liuxiran commented on issue #396: bug:got error after login

Posted by GitBox <gi...@apache.org>.
liuxiran commented on issue #396:
URL: https://github.com/apache/apisix-dashboard/issues/396#issuecomment-679187611


   about login failed: error username or password
   
   the response code is 200:
   
   ![image](https://user-images.githubusercontent.com/2561857/91061338-a4895780-e65e-11ea-9657-64f73b57dea9.png)
   
   
   but it is returned a html in fact
   
   ![image](https://user-images.githubusercontent.com/2561857/91061189-760b7c80-e65e-11ea-88bb-a3ea5699d693.png)
   
   the key to the problem is the api url: /user/login, which is not match /apisix/admin/***, so its returned by dashboard-nginx server  instead of mange-api server, so may change the login api url , is a better solution
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-dashboard] liuxiran commented on issue #396: bug:got error after login

Posted by GitBox <gi...@apache.org>.
liuxiran commented on issue #396:
URL: https://github.com/apache/apisix-dashboard/issues/396#issuecomment-679900867


   > @bzp2010 This issue is caused due to different API prefix 🤔
   > 
   > 1. All APIs use `/apisix/admin` as a prefix;
   > 2. Modify request fun on the frontend;
   > 
   > Which way would you prefer?
   
   modify ng conf can Solve this problem,but in the fe dev environment,here is another question:
   
   login api`s url is /user/login
   login page`s url is also:/user/login
   
   how to config  the fe proxy?
   so Please consider again whether to unify the interface prefix @juzhiyuan 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-dashboard] juzhiyuan commented on issue #396: bug:got error after login

Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on issue #396:
URL: https://github.com/apache/apisix-dashboard/issues/396#issuecomment-679964261


   yep, I agree using the uniform prefix for both admin API and other APIs.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-dashboard] juzhiyuan closed issue #396: bug:got error after login

Posted by GitBox <gi...@apache.org>.
juzhiyuan closed issue #396:
URL: https://github.com/apache/apisix-dashboard/issues/396


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-dashboard] juzhiyuan commented on issue #396: bug:got error after login

Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on issue #396:
URL: https://github.com/apache/apisix-dashboard/issues/396#issuecomment-679192204


   I get it and will take a look ASAP, thanks!


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-dashboard] juzhiyuan commented on issue #396: bug:got error after login

Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on issue #396:
URL: https://github.com/apache/apisix-dashboard/issues/396#issuecomment-679193421


   @bzp2010 This issue is caused due to different API prefix 🤔 
   
   1. All APIs use `/apisix/admin` as a prefix;
   2. Modify request fun on the frontend;
   
   Which way would you prefer?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org