One, the background
Recently, a lot of non-standard problems have been found when using filters to encrypt and decrypt related interface transmission.
Second, the problem
2.1 the URL naming
- The same prefix was found in the URL filtering between the filter and the gateway, resulting in some interfaces being enwrapped into the processing
/base/group/{groupId} /base/group/{groupId} /base/group/{groupId} /base/group/{groupId}
- To ensure that the URL in each controller is unique, in the case of /base/group/{groupId}, it intercepts /base/group/ in the filter or gateway, which means that the controller is processed, leading to granularity and precision issues.
2.2 table field
- When defining a table field of type, there is no related comment, no related constant class, making its meaning unclear, and when someone does not use the specification, there will be a variety of data at the beginning
- The length of some table fields is not well defined. Some table fields contain only one article, or the set length is not actually needed. For example, the status field is represented by int, which cannot exceed two digits.
Third, solutions
- Nothing else, norm, norm
- The URL must be recognizable and unique
- Table field type comments and constants must be available, length Settings should be appropriate, can be reserved
- Document and implement