20170120 daily work summary

It's almost the time of the Chinese New Year. Generally speaking, there are not many things but there are still many places to think and learn. In the past few days, I have been looking at the registration of the channel. All in all, it is finally completed today. Since then, I will write an article to consolidate my ideas. I am still an intern, and I am not very skilled in thinking. I hope that you can make good suggestions at any time after seeing it. discuss together.

      The company's demand is to expand a special channel registration link in the original channel. Because there may be multiple channel connections at the same time due to the development of the business, but because the original design was based on one page, the results submitted later did not meet the requirements. Of course, the communication with pm finally settled these. , according to different connections (ps actually means that the code behind is different). For example, the following two connections

http://localhost:8080/ment.onigiri/user/goToReg.do?fromCode=code
http://localhost:8080/ment.onigiri/user/goToReg.do?fromCode=3123

   Others are only different in the final code. Originally, my original idea was to add a code field to the table in sql to distinguish connections according to different codes. Later, when I communicated with the team leader, the connection of this field can also be used as a condition for inspection (ps I thought the connection was too long to cause problems, but in fact the content of the field is no problem. Another problem is that I did not expect the connection problem at the time. The only thing I want to get is that the code is different and judged according to the parameters... I feel that it is a problem of lack of ability. I didn't expect that the connection can be configured to obtain and then get the value according to the code. What needs to be reminded here is to pay more attention to the usual development. Configuration file. It is also a big role)

  At the same time, when a registered connection is used, the get method may be used with many parameters behind. . . . It is easy to be tampered with. The way I think for the time being is to verify the verification code when entering the controller, and then prompt on the page that the function cannot be submitted for registration. If anyone has a better way, hope to communicate. (ps in fact, the demand is to want me to hide the parameters and the result is not enough. I hope someone can give me an idea. Thank you).

 

 

 

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326586120&siteId=291194637